Triple
T13267572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anoat sector |
E315960
|
entity |
| Predicate | statusDuringEmpire |
P40055
|
FINISHED |
| Object | Imperial-controlled |
—
|
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: Imperial-controlled | Statement: [Anoat sector, statusDuringEmpire, Imperial-controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringEmpire Context triple: [Anoat sector, statusDuringEmpire, Imperial-controlled]
-
A.
statusInLateEmpire
Indicates the social, legal, or political standing an entity held during the later period of an empire.
-
B.
regionDuringEmpire
Indicates that a region existed within or was governed by a particular empire during a specified historical period.
-
C.
statusInByzantineEmpire
Indicates the role, rank, or condition an entity held within the political or social structure of the Byzantine Empire.
-
D.
legalStatusInEmpire
chosen
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
E.
functionDuringImperialEra
Indicates that a function, role, or activity occurred or was in effect during the imperial era.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:25 p.m.