Triple
T7947656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lu Xun |
E184535
|
entity |
| Predicate | resultInBattleOfYiling |
P19109
|
FINISHED |
| Object | decisive victory over Liu Bei |
—
|
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: decisive victory over Liu Bei | Statement: [Lu Xun, resultInBattleOfYiling, decisive victory over Liu Bei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultInBattleOfYiling Context triple: [Lu Xun, resultInBattleOfYiling, decisive victory over Liu Bei]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
C.
sideInBattleOfRivoli
Indicates that an entity participated as a combatant side in the Battle of Rivoli.
-
D.
sideInBattleOfHunayn
Indicates that an entity participated as a side (party or faction) in the Battle of Hunayn.
-
E.
notableBattleDuringReign
Indicates that a particular battle is notably associated with and occurred during the time span of a specific ruler’s reign.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.