Triple
T2330395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSLV Mk III |
E48387
|
entity |
| Predicate | firstOrbitalFlight |
P23257
|
FINISHED |
| Object | 5 June 2017 |
—
|
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: 5 June 2017 | Statement: [GSLV Mk III, firstOrbitalFlight, 5 June 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOrbitalFlight Context triple: [GSLV Mk III, firstOrbitalFlight, 5 June 2017]
-
A.
firstSpaceflight
Indicates that the subject entity performed, experienced, or was responsible for its earliest occurrence of traveling into outer space.
-
B.
firstSuccessfulOrbitalLaunch
Indicates that the event is the earliest instance in which a launch successfully placed a payload into a stable orbit around a celestial body.
-
C.
firstHumanInSpace
Indicates that the subject is the first human ever to travel into outer space.
-
D.
firstOrbitalMission
chosen
Indicates that the subject entity carried out or was involved in the earliest orbital spaceflight mission associated with the object entity.
-
E.
firstHumanToOrbitEarth
Indicates that the subject is the first human who successfully completed an orbital flight around Earth.
- 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_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. |
Created at: March 4, 2026, 7:50 p.m.