Triple
T10845815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S200 |
E256005
|
entity |
| Predicate | launchPadUsedWith |
P10666
|
FINISHED |
| Object | Second Launch Pad |
—
|
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: Second Launch Pad | Statement: [S200, launchPadUsedWith, Second Launch Pad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchPadUsedWith Context triple: [S200, launchPadUsedWith, Second Launch Pad]
-
A.
launchPad
chosen
Indicates a physical platform or site from which vehicles, typically rockets or spacecraft, are launched.
-
B.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
C.
controlsLaunchPad
Indicates that one entity has the authority or capability to manage, operate, or direct the use of a launch pad.
-
D.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
E.
launchPadModifications
Indicates modifications or changes made to a launch pad in preparation for or support of launch operations.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.