Triple
T27493385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwin II |
E693953
|
entity |
| Predicate | successorStateReplacedBy |
P187027
|
FINISHED |
| Object | restored Byzantine Empire |
—
|
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: restored Byzantine Empire | Statement: [Baldwin II, successorStateReplacedBy, restored Byzantine Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorStateReplacedBy Context triple: [Baldwin II, successorStateReplacedBy, restored Byzantine Empire]
-
A.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
B.
successorStateOver
Indicates that one state directly follows another in an ordered progression or sequence over a given dimension or context.
-
C.
successorStateUse
Indicates that one state or condition directly follows and is used as the next state resulting from a prior state or action.
-
D.
successorStateClaimedBy
Indicates that a particular state asserts itself as the legal or political successor to another state.
-
E.
successorStateRepresentedLater
Indicates that one state is a later representation or subsequent version of another state in a temporal or sequential progression.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: April 27, 2026, 1:06 p.m.