Triple
T11145997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-XL |
E263670
|
entity |
| Predicate | launchVehicleFamilyRole |
P52887
|
FINISHED |
| Object | high-powered PSLV variant |
—
|
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: high-powered PSLV variant | Statement: [PSLV-XL, launchVehicleFamilyRole, high-powered PSLV variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleFamilyRole Context triple: [PSLV-XL, launchVehicleFamilyRole, high-powered PSLV variant]
-
A.
launchVehicleRole
chosen
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
-
B.
launchVehicleFamilyAbbreviation
Indicates the abbreviated designation used to refer to a particular launch vehicle family.
-
C.
launchVehicleType
Indicates the type or category of launch vehicle used to carry a payload or mission into space.
-
D.
launchVehicleProvider
Indicates the entity that supplies or operates the launch vehicle used to carry a payload into space.
-
E.
usedOnLaunchVehicleFamily
Indicates that something (such as a component, system, or technology) is employed or implemented on a particular family of launch vehicles.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.