Triple
T33840151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLSF |
E867337
|
entity |
| Predicate | primaryRocket |
P147123
|
FINISHED |
| Object | Polar Satellite Launch Vehicle |
E46132
|
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: Polar Satellite Launch Vehicle | Statement: [PLSF, primaryRocket, Polar Satellite Launch Vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRocket Context triple: [PLSF, primaryRocket, Polar Satellite Launch Vehicle]
-
A.
hasMainRocket
Indicates that an entity is equipped with or associated with a primary rocket used as its main propulsion or launch system.
-
B.
usedRocket
Indicates that an entity employed a particular rocket as a tool, vehicle, or means to carry out an action or mission.
-
C.
coreLaunchVehicle
chosen
Indicates that one entity serves as the primary launch vehicle used to propel another entity (such as a payload or mission) into space.
-
D.
primaryLaunchVehicleType
Indicates the type or category of launch vehicle that is primarily used to carry a payload into space.
-
E.
rocketEngine
Indicates that an entity functions as, or is equipped with, a rocket engine used to generate thrust for propulsion.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae340ff48190ae882b4779a794db |
completed | June 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.