Triple
T36571789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E902138
|
entity |
| Predicate | succeedsCharacter |
P43223
|
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, succeedsCharacter, Richard III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeedsCharacter Context triple: [Richmond, succeedsCharacter, Richard III]
-
A.
successorCharacter
Indicates that one character directly follows another in a sequence, such as in text, ordering, or narrative progression.
-
B.
successorForCharacters
Indicates that one character directly follows or replaces another in a sequence or narrative.
-
C.
followedByCharacter
Indicates that one character comes immediately after another character in a sequence or ordering.
-
D.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
-
E.
succeedsTo
chosen
Indicates that one entity takes over a role, position, or function previously held by another entity, following it in sequence or authority.
- 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_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: May 3, 2026, 4:11 p.m.