Triple
T2987257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Kennedy Air Force Station Launch Complex 19 |
E80655
|
entity |
| Predicate | hasLaunchUmbilicalTower |
P8955
|
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: [Cape Kennedy Air Force Station Launch Complex 19, hasLaunchUmbilicalTower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchUmbilicalTower Context triple: [Cape Kennedy Air Force Station Launch Complex 19, hasLaunchUmbilicalTower, yes]
-
A.
hasControlTower
Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
-
B.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
C.
hasTower
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
D.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
E.
hasPylon
Indicates that one entity possesses, includes, or is equipped with a pylon as part of its structure or configuration.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c88f608190bf734e0b744bf3d1 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.