Triple
T32156212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch Complex 37B |
E821297
|
entity |
| Predicate | historicalEraOfSaturnLaunches |
P200366
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Space Launch Complex 37B, historicalEraOfSaturnLaunches, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfSaturnLaunches Context triple: [Space Launch Complex 37B, historicalEraOfSaturnLaunches, 1960s]
-
A.
spaceShuttleEra
Indicates that something occurs, exists, or is relevant during the period when space shuttles were actively developed, operated, or predominant in spaceflight.
-
B.
saturnReleaseYear
Indicates the year in which something was released specifically for or on the Saturn platform or system.
-
C.
spaceLaunchDate
Indicates the date on which a spacecraft, rocket, or space mission is launched.
-
D.
firstSuccessfulOrbitalLaunch
Indicates that the event is the earliest instance in which a launch successfully placed a payload into a stable orbit around a celestial body.
-
E.
spaceflightDate
Indicates the date on which a spaceflight event occurs or is scheduled to occur.
- F. None of above. chosen
Provenance (4 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_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
| PDg | Predicate description generation | batch_69ff84dec2848190b67a497d025c8880 |
completed | May 9, 2026, 7:02 p.m. |
Created at: May 1, 2026, 12:32 a.m.