Triple
T31910252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Wei |
E814660
|
entity |
| Predicate | linkedWarlord |
P109086
|
FINISHED |
| Object | Cao Cao |
—
|
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: Cao Cao | Statement: [King of Wei, linkedWarlord, Cao Cao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedWarlord Context triple: [King of Wei, linkedWarlord, Cao Cao]
-
A.
wargBond
Indicates a special bond or partnership between a warg and another entity, typically involving loyalty, cooperation, or shared purpose.
-
B.
warlordCharacter
chosen
Indicates that one entity plays the role or has the characteristics of a warlord in relation to another entity or within a given context.
-
C.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
-
D.
isWarHeroOf
Indicates that one entity is recognized as a war hero in relation to, or on behalf of, another entity (such as a country, group, or cause).
-
E.
producedWarlord
Indicates that an entity is responsible for bringing about, creating, or giving rise to a particular warlord.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 12:01 a.m.