Triple
T32202649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andronikos IV Palaiologos |
E822582
|
entity |
| Predicate | succeededAsHeirBy |
P79814
|
FINISHED |
| Object | Manuel II Palaiologos |
—
|
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: Manuel II Palaiologos | Statement: [Andronikos IV Palaiologos, succeededAsHeirBy, Manuel II Palaiologos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAsHeirBy Context triple: [Andronikos IV Palaiologos, succeededAsHeirBy, Manuel II Palaiologos]
-
A.
succeededAsHeir
chosen
Indicates that one entity became the heir in place of, or following, another entity, typically upon the latter’s death or abdication.
-
B.
madeHeirBy
Indicates that one entity is designated or appointed as the heir of another entity.
-
C.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
-
D.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
E.
resultedInSuccessionTo
Indicates that one event, action, or circumstance caused or led directly to a change in who holds a position, title, or role, resulting in a new successor taking over.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 12:36 a.m.