Triple
T12337181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Canaveral LC-37B |
E294117
|
entity |
| Predicate | hasLaunchInfrastructure |
P2560
|
FINISHED |
| Object | fixed umbilical tower |
—
|
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: fixed umbilical tower | Statement: [Cape Canaveral LC-37B, hasLaunchInfrastructure, fixed umbilical tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchInfrastructure Context triple: [Cape Canaveral LC-37B, hasLaunchInfrastructure, fixed umbilical tower]
-
A.
hasGlobalInfrastructure
Indicates that an entity possesses infrastructure, facilities, or operational capabilities that are distributed across multiple countries or regions worldwide.
-
B.
hasInfrastructureScale
Indicates the relative size, capacity, or extent of infrastructure associated with or supporting an entity.
-
C.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
D.
hasInfrastructureOwner
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
E.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f6683e881908920e1fee02a14e3 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.