Triple
T31687086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordelia Foxx |
E808688
|
entity |
| Predicate | predecessorAsSupreme |
P126723
|
FINISHED |
| Object | Fiona Goode |
—
|
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: Fiona Goode | Statement: [Cordelia Foxx, predecessorAsSupreme, Fiona Goode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsSupreme Context triple: [Cordelia Foxx, predecessorAsSupreme, Fiona Goode]
-
A.
predecessorAsSupremeRuler
chosen
Indicates that one entity previously held the position of supreme ruler immediately before another entity.
-
B.
predecessorAsDeFactoRuler
Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
-
C.
predecessorAsKing
Indicates that one entity previously held the position of king immediately before the other entity.
-
D.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
E.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 30, 2026, 11:07 p.m.