Triple
T34178868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew Kantakouzenos |
E876753
|
entity |
| Predicate | wasCoEmperorWith |
P10356
|
FINISHED |
| Object | John V 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: John V Palaiologos | Statement: [Matthew Kantakouzenos, wasCoEmperorWith, John V Palaiologos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCoEmperorWith Context triple: [Matthew Kantakouzenos, wasCoEmperorWith, John V Palaiologos]
-
A.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
B.
coEmperorWith
chosen
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
C.
wasEmperorDuring
Indicates that a person held the position of emperor during a specified time period or historical era.
-
D.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
E.
fatherWasEmperorOf
Indicates that the person referred to as the father held the position or title of emperor of the specified entity (such as a state, empire, or territory).
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7100315948190bc23da7543715446 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.