Triple
T24126118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agni-IV |
E597804
|
entity |
| Predicate | accuracyFeature |
P100245
|
FINISHED |
| Object | high accuracy |
—
|
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: high accuracy | Statement: [Agni-IV, accuracyFeature, high accuracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accuracyFeature Context triple: [Agni-IV, accuracyFeature, high accuracy]
-
A.
curacy
Indicates that one entity serves in the role or position of a curate (assistant clergy) in relation to another entity, typically a parish or church.
-
B.
scoreFeatures
Indicates assigning quantitative scores or evaluations to a set of features based on specified criteria or models.
-
C.
accuracyDependsOn
Indicates that the accuracy of one entity or process is contingent upon, or influenced by, another entity or factor.
-
D.
recognizedFeature
chosen
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or context.
-
E.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee9086481909710c6d3291242c3 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.