Triple
T24139832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agni-III |
E598196
|
entity |
| Predicate | hasCEP |
P154987
|
FINISHED |
| Object | around 40 meters |
—
|
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: around 40 meters | Statement: [Agni-III, hasCEP, around 40 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCEP Context triple: [Agni-III, hasCEP, around 40 meters]
-
A.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
B.
hasCAS
Indicates that an entity is associated with a specific Chemical Abstracts Service (CAS) registry number identifying it as a distinct chemical substance.
-
C.
hasHCR
Indicates that an entity possesses, is associated with, or is governed by a specific Health Care Regulation (HCR).
-
D.
hasCap
Indicates that an entity possesses or is equipped with a cap or top covering.
-
E.
hasCcf
Indicates that one entity possesses, is associated with, or is characterized by a specific CCF (the exact nature of which is defined elsewhere in the model or ontology).
- 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.