Triple
T37832025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand the Great |
E943228
|
entity |
| Predicate | successorAsCountOfCastile |
P202786
|
FINISHED |
| Object | Sancho II of Castile |
—
|
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: Sancho II of Castile | Statement: [Ferdinand the Great, successorAsCountOfCastile, Sancho II of Castile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsCountOfCastile Context triple: [Ferdinand the Great, successorAsCountOfCastile, Sancho II of Castile]
-
A.
successorAsKingOfCastile
Indicates that one entity became the next king of Castile following another entity.
-
B.
successorAsRecognizedMonarchOfCastile
Indicates that one entity is the next officially acknowledged monarch of Castile following another entity.
-
C.
successorAsKingOfNavarre
Indicates that one person became the next king of Navarre following another person in the royal succession.
-
D.
successorAsQueenOfCastile
Indicates that one entity became the next reigning queen of Castile following another entity.
-
E.
successorAsKingOfLeón
Indicates that one person became the next king of León after another person, directly succeeding them on the throne.
- F. None of above. chosen
Provenance (4 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
| PDg | Predicate description generation | batch_6a00b8dfde3c81908c04ceccf67329db |
completed | May 10, 2026, 4:57 p.m. |
Created at: May 3, 2026, 4:19 p.m.