Triple
T32820540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Space Alliance |
E839422
|
entity |
| Predicate | operatedForAgency |
P3679
|
FINISHED |
| Object | NASA |
—
|
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: NASA | Statement: [United Space Alliance, operatedForAgency, NASA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedForAgency Context triple: [United Space Alliance, operatedForAgency, NASA]
-
A.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
B.
operatedFor
chosen
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
C.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
D.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
E.
operatedByOrganization
Indicates that an activity, facility, or system is run, managed, or controlled by a specific organization.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:15 a.m.