Triple
T36571777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E902138
|
entity |
| Predicate | defeatsCharacter |
P11263
|
FINISHED |
| Object | Richard III |
—
|
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: Richard III | Statement: [Richmond, defeatsCharacter, Richard III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatsCharacter Context triple: [Richmond, defeatsCharacter, Richard III]
-
A.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
B.
defendsCharacter
Indicates that one entity protects, supports, or argues in favor of another entity, especially in the face of criticism, attack, or threat.
-
C.
defeatedBy
chosen
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
D.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
-
E.
defeatSymbolizes
Indicates that an instance of defeat is used to symbolically represent or stand for another concept, state, or idea.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.