Triple
T28285007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tangdao |
E713257
|
entity |
| Predicate | opposingSideLeader |
P17525
|
FINISHED |
| Object | Emperor Wanyan Liang of Jin |
—
|
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: Emperor Wanyan Liang of Jin | Statement: [Battle of Tangdao, opposingSideLeader, Emperor Wanyan Liang of Jin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingSideLeader Context triple: [Battle of Tangdao, opposingSideLeader, Emperor Wanyan Liang of Jin]
-
A.
opposedLeader
Indicates that one entity actively resisted, challenged, or worked against the leadership or authority of another entity.
-
B.
opposedLeaderSide2
Indicates that the second leader or side is in opposition to another leader or side in a conflict or contest.
-
C.
primaryOpposingLeader
chosen
Indicates that one entity serves as the main or chief leader directly opposing another entity in a conflict, competition, or political context.
-
D.
oppositionLeader
Indicates that one entity serves as the primary political leader of the opposition in relation to another governing entity.
-
E.
negotiatingPartyLeader
Indicates that the subject is the primary representative or leader directing or overseeing a party involved in a negotiation.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 11:25 p.m.