Triple
T27343508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantis (OV-104) |
E684170
|
entity |
| Predicate | finalMissionRole |
P45245
|
FINISHED |
| Object | final flight of the Space Shuttle program |
—
|
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: final flight of the Space Shuttle program | Statement: [Atlantis (OV-104), finalMissionRole, final flight of the Space Shuttle program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMissionRole Context triple: [Atlantis (OV-104), finalMissionRole, final flight of the Space Shuttle program]
-
A.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
B.
finalMissionPhase
Indicates that an entity is in, or corresponds to, the concluding or last phase of a mission.
-
C.
finalPeriodRole
Indicates the role or function an entity holds during the final period or concluding phase of a specified interval or process.
-
D.
roleInMissions
chosen
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
E.
missionEnd
Indicates that a mission has concluded or reached its final state or outcome.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 11:44 a.m.