Triple
T26728232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Despotate of Arta |
E673891
|
entity |
| Predicate | rulingElites |
P89474
|
FINISHED |
| Object | Albanian nobility |
—
|
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: Albanian nobility | Statement: [Despotate of Arta, rulingElites, Albanian nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingElites Context triple: [Despotate of Arta, rulingElites, Albanian nobility]
-
A.
dominantPoliticalElite
Indicates that one group or individual holds primary political power and influence over others within a given system or context.
-
B.
hadRulingClass
chosen
Indicates that a particular group or class held dominant political, economic, or social power over a society or entity.
-
C.
ethnicGroupOfRulers
Indicates the ethnic group to which the rulers of a given political or territorial entity belong or belonged.
-
D.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
E.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6180c6ba081908b82e0a76fdb94e8 |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:43 a.m.