Triple
T26719888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle landings |
E673672
|
entity |
| Predicate | backupLandingSite |
P127850
|
FINISHED |
| Object | White Sands Space Harbor |
—
|
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: White Sands Space Harbor | Statement: [Space Shuttle landings, backupLandingSite, White Sands Space Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupLandingSite Context triple: [Space Shuttle landings, backupLandingSite, White Sands Space Harbor]
-
A.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
B.
alternateLandingSiteForMission
chosen
Indicates that a location serves as a backup or contingency landing site designated for a specific mission.
-
C.
servesAsBackupFor
Indicates that one entity functions as a substitute or fallback that can take over the role or responsibilities of another entity if needed.
-
D.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
E.
reserveLocation
Indicates that an entity designates or sets aside a specific place for a particular use, purpose, or future activity.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:40 a.m.