Triple
T28717215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares program |
E729991
|
entity |
| Predicate | agencyHeadquarters |
P62
|
FINISHED |
| Object | Johnson Space Center (fictional context) |
—
|
NE NERFINISHED |
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: Johnson Space Center (fictional context) | Statement: [Ares program, agencyHeadquarters, Johnson Space Center (fictional context)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agencyHeadquarters Context triple: [Ares program, agencyHeadquarters, Johnson Space Center (fictional context)]
-
A.
associationHeadquarters
Indicates the location where an association’s main administrative offices or central headquarters are based.
-
B.
employerHeadquarters
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
-
C.
headquartersLocation
chosen
Indicates the place where an organization’s main administrative center or principal office is located.
-
D.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
E.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
- F. None of above.
Provenance (3 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:51 a.m.