Triple
T2330410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSLV Mk III |
E48387
|
entity |
| Predicate | reliabilityRecord |
P38972
|
FINISHED |
| Object | multiple successful orbital 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: multiple successful orbital missions | Statement: [GSLV Mk III, reliabilityRecord, multiple successful orbital missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliabilityRecord Context triple: [GSLV Mk III, reliabilityRecord, multiple successful orbital missions]
-
A.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
B.
attestedBy
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
C.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
D.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
-
E.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc2fa25c8190858c1c541b914f4c |
completed | March 7, 2026, 6:56 a.m. |
Created at: March 4, 2026, 7:50 p.m.