Triple
T11000512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-CA |
E259990
|
entity |
| Predicate | launchHistory |
P42105
|
FINISHED |
| Object | used in multiple ISRO missions |
—
|
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: used in multiple ISRO missions | Statement: [PSLV-CA, launchHistory, used in multiple ISRO missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchHistory Context triple: [PSLV-CA, launchHistory, used in multiple ISRO missions]
-
A.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
B.
missionHistory
Indicates the record of past missions or assignments associated with an entity, including their occurrence and relevant details.
-
C.
launchRecord
chosen
Indicates the act of initiating or starting a recorded instance of a process, event, or operation.
-
D.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
E.
movementHistory
Indicates a record of how an entity has moved over time, capturing the sequence, timing, and possibly locations of its movements.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d68b608190a8d016b9383e82f8 |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.