Triple
T34729463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LC-17A |
E1001167
|
entity |
| Predicate | hasLaunchComplexNumber |
P29508
|
FINISHED |
| Object | 17A |
—
|
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: 17A | Statement: [LC-17A, hasLaunchComplexNumber, 17A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchComplexNumber Context triple: [LC-17A, hasLaunchComplexNumber, 17A]
-
A.
testLaunchComplex
Indicates a relationship where a launch complex is used or involved in testing activities, such as trial launches or validation procedures.
-
B.
hasLaunchPadNumber
chosen
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
C.
launchedByMission
Indicates that an object or entity was sent or initiated as part of a specific mission.
-
D.
spacecraftLaunchAssociatedWith
Indicates a relationship where a spacecraft launch is connected or linked to another event, object, or entity involved in or affected by that launch.
-
E.
hasLaunchPadsFor
Indicates that one entity provides or contains launch pads intended for use by another entity.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 3, 2026, 3:59 p.m.