Triple
T27541579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gaixia |
E695249
|
entity |
| Predicate | decisiveCommander |
P114662
|
FINISHED |
| Object | Han Xin |
—
|
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: Han Xin | Statement: [Battle of Gaixia, decisiveCommander, Han Xin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveCommander Context triple: [Battle of Gaixia, decisiveCommander, Han Xin]
-
A.
strategicCommand
Indicates that one entity issues high-level, overarching directives or plans that guide the actions or decisions of another entity.
-
B.
opposingCommander
Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
-
C.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
D.
frequentCommander
Indicates that one entity regularly serves as a commander or leader over another entity in repeated or numerous instances.
-
E.
commanderOfVictoriousSide
chosen
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 1:31 p.m.