Triple
T29296319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Θεόδωρος Α΄ Παλαιολόγος |
E742840
|
entity |
| Predicate | δυναστεία |
P1547
|
FINISHED |
| Object | Παλαιολόγοι |
—
|
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: Παλαιολόγοι | Statement: [Θεόδωρος Α΄ Παλαιολόγος, δυναστεία, Παλαιολόγοι]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: δυναστεία Context triple: [Θεόδωρος Α΄ Παλαιολόγος, δυναστεία, Παλαιολόγοι]
-
A.
dynasty
chosen
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
B.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
C.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
D.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
E.
dynasticUse
Indicates the use of something (such as a name, title, symbol, or resource) in a way that is tied to or characteristic of a particular dynasty or ruling family.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654459b481908684b3efa19d5bd5 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:06 p.m.