Triple
T37032284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tripartite struggle for Kannauj |
E916527
|
entity |
| Predicate | centerOfConflict |
P96925
|
FINISHED |
| Object | Kannauj |
—
|
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: Kannauj | Statement: [tripartite struggle for Kannauj, centerOfConflict, Kannauj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerOfConflict Context triple: [tripartite struggle for Kannauj, centerOfConflict, Kannauj]
-
A.
centralConflictIn
chosen
Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
-
B.
regionOfConflict
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
C.
conflictGround
Indicates that one entity is the cause, basis, or subject matter of a conflict involving another entity.
-
D.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
E.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved entities.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.