Triple
T23782364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Basantar |
E587849
|
entity |
| Predicate | equipmentUsedIndia |
P12755
|
FINISHED |
| Object | Centurion tanks |
—
|
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: Centurion tanks | Statement: [Battle of Basantar, equipmentUsedIndia, Centurion tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentUsedIndia Context triple: [Battle of Basantar, equipmentUsedIndia, Centurion tanks]
-
A.
scriptUsedInIndia
Indicates that a particular writing system or script is used within the geographical or cultural context of India.
-
B.
typeOfEquipmentUsed
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
C.
equipmentProvider
Indicates that one entity supplies or makes available equipment for use by another entity.
-
D.
equipmentIncludes
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
E.
hardwareUsedBy
chosen
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62d7c608190b5fd0cf35f5faf42 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.