Triple
T27075333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 51 |
E685447
|
entity |
| Predicate | commanderAgency |
P115272
|
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: [Expedition 51, commanderAgency, NASA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderAgency Context triple: [Expedition 51, commanderAgency, NASA]
-
A.
deputyCommanderAgency
Indicates that one entity serves as the deputy commander within, or on behalf of, a specified agency.
-
B.
commanderForGovernment
chosen
Indicates that an entity serves as a military or organizational commander on behalf of, or within the authority structure of, a specific government.
-
C.
componentAgency
Indicates that one entity functions as a constituent or subordinate agency within the organizational structure of another agency.
-
D.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
E.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 8:30 a.m.