Triple
T36486435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M3 |
E898944
|
entity |
| Predicate | launchAgencyOfHostMission |
P188483
|
FINISHED |
| Object | Indian Space Research Organisation |
—
|
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: Indian Space Research Organisation | Statement: [M3, launchAgencyOfHostMission, Indian Space Research Organisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAgencyOfHostMission Context triple: [M3, launchAgencyOfHostMission, Indian Space Research Organisation]
-
A.
spaceMissionStart
Indicates the point in time or event at which a space mission officially begins.
-
B.
launchSpacecraft
Indicates initiating the sending of a spacecraft from a launch site into space, typically by activating and controlling its launch vehicle.
-
C.
launchOnMission
Indicates initiating the sending of an entity (typically a vehicle, spacecraft, or device) to carry out a specific mission or operation.
-
D.
missionTypeEstablished
Indicates that a specific type or category of mission has been formally defined and put into effect.
-
E.
launchedByMission
Indicates that an object or entity was sent or initiated as part of a specific mission.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:10 p.m.