Triple
T23844771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agni-V |
E591088
|
entity |
| Predicate | firstTestFlightDate |
P24224
|
FINISHED |
| Object | 2012-04-19 |
—
|
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: 2012-04-19 | Statement: [Agni-V, firstTestFlightDate, 2012-04-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTestFlightDate Context triple: [Agni-V, firstTestFlightDate, 2012-04-19]
-
A.
firstFreeFlightTest
Indicates that the event is the initial instance in which an aircraft, spacecraft, or similar vehicle is flown freely without external constraints or tethering.
-
B.
firstUncrewedTestFlight
chosen
Indicates the event of conducting the initial test flight of a vehicle or system without any crew onboard.
-
C.
allegedFirstFlightDate
Indicates the date on which an entity is claimed or reported (but not necessarily confirmed) to have made its first flight.
-
D.
firstFlybyDate
Indicates the date on which an object or mission first performed a flyby of a target body or location.
-
E.
firstUncrewedTestFlightMission
Indicates that the subject is the first mission in which a spacecraft or launch system is tested in flight without any crew onboard.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88a4b948190989a261e79b996a6 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.