Triple
T32156202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch Complex 37B |
E821297
|
entity |
| Predicate | hasSisterPad |
P97757
|
FINISHED |
| Object | Space Launch Complex 37A |
—
|
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: Space Launch Complex 37A | Statement: [Space Launch Complex 37B, hasSisterPad, Space Launch Complex 37A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterPad Context triple: [Space Launch Complex 37B, hasSisterPad, Space Launch Complex 37A]
-
A.
hasSiblingPad
chosen
Indicates that one entity is a sibling of another entity, specifically in the context of a pad or pad-related structure.
-
B.
hasSister
Indicates that one entity is the sister of another entity.
-
C.
hasSisterChair
Indicates that one chair is related to another chair as its sister, typically implying a closely associated or counterpart chair within the same set or context.
-
D.
hasPad
Indicates that one entity possesses, is equipped with, or is associated with a pad (such as a cushion, tablet, or protective surface).
-
E.
hasSisterChannel
Indicates that one media channel is related to another as its sister channel, typically under common ownership or branding.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 12:32 a.m.