Triple
T1053299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand VI of Spain |
E22745
|
entity |
| Predicate | successorSelection |
P7979
|
FINISHED |
| Object | throne passed to his half-brother Charles III |
—
|
LITERAL FINISHED |
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: throne passed to his half-brother Charles III | Statement: [Ferdinand VI of Spain, successorSelection, throne passed to his half-brother Charles III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorSelection Context triple: [Ferdinand VI of Spain, successorSelection, throne passed to his half-brother Charles III]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorDesignated
chosen
Indicates that one entity has been formally chosen or named to take over the role, position, or responsibilities of another entity in the future.
-
C.
successorProtocol
Indicates that one protocol directly follows and replaces another in sequence or versioning.
-
D.
successorProcess
Indicates that one process directly follows another in a defined sequence or workflow.
-
E.
successorOperator
Indicates that one operator directly follows another in a defined sequence or ordering.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b644088190a1f0f00f97941298 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.