Triple
T308089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Energy Astrophysics Division |
E6345
|
entity |
| Predicate | supportsCommunity |
P11337
|
FINISHED |
| Object | astronomers |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: astronomers | Statement: [High Energy Astrophysics Division, supportsCommunity, astronomers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCommunity Context triple: [High Energy Astrophysics Division, supportsCommunity, astronomers]
-
A.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
B.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
C.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
-
D.
hasOnlineCommunity
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
-
E.
usedInCommunity
Indicates that something is employed, practiced, or applied within a particular community or communal context.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea3289608190a36c20a47761c6e4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93f38308190b4b480c951f1a1c3 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2af1388190b93235602ace679e |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.