Triple
T28774599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kantakouzenos |
E726498
|
entity |
| Predicate | producedDespot |
P187572
|
FINISHED |
| Object | Manuel Kantakouzenos |
—
|
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 Kantakouzenos | Statement: [Kantakouzenos, producedDespot, Manuel Kantakouzenos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedDespot Context triple: [Kantakouzenos, producedDespot, Manuel Kantakouzenos]
-
A.
producedTsar
Indicates that an entity (such as a person, group, or process) brought about or created a tsar as a result or outcome.
-
B.
producedEmpress
Indicates that one entity created, generated, or brought about the existence or status of an empress.
-
C.
firstDespot
Indicates that the subject is the earliest or original ruler with despotic authority over the object (such as a state, territory, or people).
-
D.
producedEmperor
Indicates that one entity brought about, created, or was responsible for the rise or existence of an emperor.
-
E.
producedSaint
Indicates that an entity (such as a place, group, or lineage) has given rise to or brought forth a particular saint.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 28, 2026, 6:17 a.m.