Triple
T27959814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun family of Eastern Wu |
E704549
|
entity |
| Predicate | notableBattleInvolvingClan |
P191433
|
FINISHED |
| Object | Battle of Red Cliffs |
—
|
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: Battle of Red Cliffs | Statement: [Sun family of Eastern Wu, notableBattleInvolvingClan, Battle of Red Cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBattleInvolvingClan Context triple: [Sun family of Eastern Wu, notableBattleInvolvingClan, Battle of Red Cliffs]
-
A.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
B.
clanStruggle
Indicates a conflict or power struggle occurring between different clans or clan-based groups.
-
C.
battleFoughtBy
chosen
Indicates that a specific battle was fought by a particular participant or group of participants.
-
D.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
E.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: April 27, 2026, 7:30 p.m.