Triple
T26529529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demo-2 |
E670780
|
entity |
| Predicate | astronautAgency |
P122385
|
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: [Demo-2, astronautAgency, NASA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronautAgency Context triple: [Demo-2, astronautAgency, NASA]
-
A.
astronautTrainingAgency
Indicates that an agency is responsible for training astronauts or overseeing astronaut training programs.
-
B.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
-
C.
spaceAgency
Indicates that one entity is a space agency that operates, manages, or oversees space-related missions, programs, or activities on behalf of the other entity.
-
D.
hostSpaceAgency
Indicates that one entity serves as the space agency that organizes, manages, or officially represents space-related activities for another entity (such as a mission, event, or facility).
-
E.
isAstronautOf
chosen
Indicates that a person serves as an astronaut who is a member of, or assigned to, a particular space agency, mission, or spacecraft.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:34 a.m.