Triple
T36565099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Complex 37 |
E901954
|
entity |
| Predicate | hasFixedUmbilicalTower |
P201822
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Launch Complex 37, hasFixedUmbilicalTower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedUmbilicalTower Context triple: [Launch Complex 37, hasFixedUmbilicalTower, yes]
-
A.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
B.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
C.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
D.
hasTowerNumber
Indicates that an entity is associated with a specific tower identified by a particular number.
-
E.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
- F. None of above. chosen
Provenance (4 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
| PDg | Predicate description generation | batch_6a00262cc9408190b95076a2d3da057d |
completed | May 10, 2026, 6:31 a.m. |
Created at: May 3, 2026, 4:11 p.m.