Triple
T23415032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Oropesa |
E560180
|
entity |
| Predicate | successorTitlePossible |
P152169
|
FINISHED |
| Object | Duke of Oropesa |
—
|
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: Duke of Oropesa | Statement: [Count of Oropesa, successorTitlePossible, Duke of Oropesa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitlePossible Context triple: [Count of Oropesa, successorTitlePossible, Duke of Oropesa]
-
A.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
B.
successorTitleContext
Indicates the contextual circumstances or framework under which one title succeeds another.
-
C.
successorTitleForHolders
Indicates that one title is the official successor title that replaces or follows the titles previously held by certain holders.
-
D.
successorTitleIntegratedInto
Indicates that the title of a successor entity has been merged into and is now part of another title or entity.
-
E.
successorTitleSponsor
Indicates that one entity becomes the next official title sponsor replacing another entity.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a514b1d08190bbde2c3714c996fd |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:39 p.m.