Triple
T13252640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 1 |
E315571
|
entity |
| Predicate | launchSite |
P4384
|
FINISHED |
| Object | LC-19 |
E200644
|
NE 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: LC-19 | Statement: [Gemini 1, launchSite, LC-19]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LC-19 Context triple: [Gemini 1, launchSite, LC-19]
-
A.
LC-19
chosen
LC-19 is a historic launch complex at Cape Canaveral used extensively during NASA’s early crewed spaceflight programs, including the Gemini missions.
-
B.
LC-5
LC-5 is a historic launch complex at Cape Canaveral used for early U.S. crewed spaceflights during the Mercury program.
-
C.
LC-18A
LC-18A is a launch complex at Cape Canaveral used historically for early U.S. rocket launches, including the Vanguard program.
-
D.
LR-91
The LR-91 is a liquid-fueled rocket engine developed by Aerojet and used as the upper-stage propulsion system on various Titan family launch vehicles.
-
E.
LC-36A
LC-36A is one of the launch pads at Cape Canaveral’s Launch Complex 36, historically used for Atlas rocket launches.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98f73423c8190932a9edac56df383 |
completed | April 11, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a3b8ca48190863aff25f12d0e7e |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:24 p.m.