Triple
T28774732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Δεσπότης Μυστρά |
E726502
|
entity |
| Predicate | ιστορικὴΠερίοδος |
P83770
|
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.
historical era
chosen
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
D.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
E.
historicalConcept
Indicates that something represents, embodies, or is recognized as a concept, idea, or notion rooted in or primarily relevant to a past historical context.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:17 a.m.