Triple
T23844462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arjun main battle tank |
E591081
|
entity |
| Predicate | armourName |
P90185
|
FINISHED |
| Object | Kanchan armour |
—
|
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: Kanchan armour | Statement: [Arjun main battle tank, armourName, Kanchan armour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armourName Context triple: [Arjun main battle tank, armourName, Kanchan armour]
-
A.
armorName
chosen
Indicates that an entity has or is associated with a specific name identifying its armor.
-
B.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
C.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
D.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another entity.
-
E.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
- 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.