Triple
T27674009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSLC |
E697732
|
entity |
| Predicate | hasLaunchPadType |
P185937
|
FINISHED |
| Object | orbital 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: orbital launch pad | Statement: [TSLC, hasLaunchPadType, orbital launch pad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchPadType Context triple: [TSLC, hasLaunchPadType, orbital launch pad]
-
A.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
B.
controlsLaunchPad
Indicates that one entity has the authority or capability to manage, operate, or direct the use of a launch pad.
-
C.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
-
D.
launchPad
Indicates a physical platform or site from which vehicles, typically rockets or spacecraft, are launched.
-
E.
hasLaunchRange
Indicates that one entity (typically a weapon or vehicle) has the capability to be launched or to operate effectively within a specified distance range from a target or origin.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 27, 2026, 2:42 p.m.