Triple
T27959467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Cao |
E704538
|
entity |
| Predicate | notableRivalState |
P172365
|
FINISHED |
| Object | Shu Han |
—
|
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: Shu Han | Statement: [House of Cao, notableRivalState, Shu Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRivalState Context triple: [House of Cao, notableRivalState, Shu Han]
-
A.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
B.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
C.
hasRivalState
chosen
Indicates that one state maintains a rivalry or competitive opposition with another state.
-
D.
notableRivalOpponent
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
E.
opponentStateAbbreviation
Indicates the abbreviated state code associated with the opponent in the relationship or event.
- 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_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
Created at: April 27, 2026, 7:30 p.m.