Triple
T24139842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agni-III |
E598196
|
entity |
| Predicate | testFiredBy |
P154988
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [Agni-III, testFiredBy, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testFiredBy Context triple: [Agni-III, testFiredBy, India]
-
A.
firedBy
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
B.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
C.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
D.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
E.
firedAt
Indicates that one entity discharged a weapon or projectile in the direction of another entity.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e004fd38819080135a069e98a3e1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:28 p.m.