Triple
T28246460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Xiaocheng of Zhao |
E712181
|
entity |
| Predicate | opponentStateAtBattleOfChangping |
P165432
|
FINISHED |
| Object | State of Qin |
—
|
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: State of Qin | Statement: [King Xiaocheng of Zhao, opponentStateAtBattleOfChangping, State of Qin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentStateAtBattleOfChangping Context triple: [King Xiaocheng of Zhao, opponentStateAtBattleOfChangping, State of Qin]
-
A.
sideInBattleOfYiling
Indicates that an entity participated as a side or faction in the Battle of Yiling.
-
B.
opponentInBattleOfRaphia
Indicates that two entities were opposing sides against each other in the historical Battle of Raphia.
-
C.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
D.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
E.
refersToPersonNotableBattle
Indicates that a person is associated with or identified by a specific notable battle in which they played a significant role.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 11:01 p.m.