Triple
T36764356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV |
E908293
|
entity |
| Predicate | primaryLaunchPad |
P10666
|
FINISHED |
| Object | First Launch Pad, SDSC SHAR |
E867332
|
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: First Launch Pad, SDSC SHAR | Statement: [PSLV, primaryLaunchPad, First Launch Pad, SDSC SHAR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLaunchPad Context triple: [PSLV, primaryLaunchPad, First Launch Pad, SDSC SHAR]
-
A.
launchPad
chosen
Indicates a physical platform or site from which vehicles, typically rockets or spacecraft, are launched.
-
B.
launchPadInterface
Indicates a functional connection through which a launch pad system communicates with, controls, or exchanges data with other components or users.
-
C.
controlsLaunchPad
Indicates that one entity has the authority or capability to manage, operate, or direct the use of a launch pad.
-
D.
helpedLaunch
Indicates that one entity played a significant role in initiating, starting, or bringing another entity (such as a project, product, or organization) into operation or public release.
-
E.
hasLaunchPadsFor
Indicates that one entity provides or contains launch pads intended for use by another entity.
- F. None of above.
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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3c17457a9c8190a756a4414170ec3a |
completed | June 24, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.