Triple
T32156197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch Complex 37B |
E821297
|
entity |
| Predicate | historicallySupportedRocket |
P90427
|
FINISHED |
| Object | Saturn I |
—
|
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: Saturn I | Statement: [Space Launch Complex 37B, historicallySupportedRocket, Saturn I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallySupportedRocket Context triple: [Space Launch Complex 37B, historicallySupportedRocket, Saturn I]
-
A.
supportsRocketFamily
chosen
Indicates that one entity provides the necessary infrastructure, compatibility, or services to accommodate or operate a specified family of rockets.
-
B.
testedRocketsIn
Indicates that an entity conducted tests of rockets within a specified location or context.
-
C.
usedRocket
Indicates that an entity employed a particular rocket as a tool, vehicle, or means to carry out an action or mission.
-
D.
usedByRocket
Indicates that something serves as a component, resource, or tool that is utilized by a rocket.
-
E.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
- 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_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 1, 2026, 12:32 a.m.