Triple
T38169054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Complex 17A |
E1000017
|
entity |
| Predicate | hasAdjacentPad |
P5707
|
FINISHED |
| Object | Launch Complex 17B |
—
|
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: Launch Complex 17B | Statement: [Launch Complex 17A, hasAdjacentPad, Launch Complex 17B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentPad Context triple: [Launch Complex 17A, hasAdjacentPad, Launch Complex 17B]
-
A.
hasSiblingPad
Indicates that one entity is a sibling of another entity, specifically in the context of a pad or pad-related structure.
-
B.
hasPad
Indicates that one entity possesses, is equipped with, or is associated with a pad (such as a cushion, tablet, or protective surface).
-
C.
hasAdjacentQuadrant
Indicates that one quadrant is directly next to another quadrant, sharing a common boundary or side.
-
D.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
-
E.
isAdjacentTo
chosen
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:29 p.m.