Triple
T32713726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hanzhong |
E836464
|
entity |
| Predicate | yearOfKeyClash |
P193489
|
FINISHED |
| Object | 219 |
—
|
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: 219 | Statement: [Battle of Hanzhong, yearOfKeyClash, 219]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfKeyClash Context triple: [Battle of Hanzhong, yearOfKeyClash, 219]
-
A.
firstCollisionsYear
Indicates the year in which the first collisions or interaction events occurred between the relevant entities.
-
B.
chosenPrefixCollisionYear
Indicates the year in which a specific prefix was selected or identified as having a collision with another prefix.
-
C.
crashYear
Indicates the year in which a crash or collision event occurred.
-
D.
yearChallenged
Indicates the specific year in which a challenge, dispute, or contestation of something occurred.
-
E.
majorConflictYear
Indicates the year in which a major conflict, such as a war or large-scale violent confrontation, took place or reached a defining point.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: May 1, 2026, 1:11 a.m.