Triple
T36705718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOM camera |
E906354
|
entity |
| Predicate | launchVehicleOfHostMission |
P4020
|
FINISHED |
| Object | PSLV-XL |
—
|
NE NERFINISHED |
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: PSLV-XL | Statement: [MOM camera, launchVehicleOfHostMission, PSLV-XL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleOfHostMission Context triple: [MOM camera, launchVehicleOfHostMission, PSLV-XL]
-
A.
launchVehicle
chosen
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
B.
launchAgencyOfHostMission
Indicates that an entity serves as the launch agency responsible for conducting or managing the host mission.
-
C.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
D.
launchVehicleComponentOf
Indicates that one entity is a component or part of a launch vehicle used to send payloads into space.
-
E.
launchSpacecraft
Indicates initiating the sending of a spacecraft from a launch site into space, typically by activating and controlling its launch vehicle.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:12 p.m.