Triple
T31409616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman absolutism |
E801223
|
entity |
| Predicate | existedInTerritory |
P157368
|
FINISHED |
| Object | Anatolia |
—
|
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: Anatolia | Statement: [Ottoman absolutism, existedInTerritory, Anatolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedInTerritory Context triple: [Ottoman absolutism, existedInTerritory, Anatolia]
-
A.
endedInTerritory
Indicates that an event or action concluded within the bounds of a specified territory or geographic area.
-
B.
territoryOriginallyIncluded
Indicates that an earlier or original territorial boundary encompassed the referenced area or entity.
-
C.
existedWithinSovereign
chosen
Indicates that one entity existed geographically or politically inside the territorial boundaries or jurisdiction of a sovereign state or authority.
-
D.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
E.
hasDefinedTerritory
Indicates that an entity possesses a specific, delimited geographic or conceptual area over which it has recognized control or jurisdiction.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:36 p.m.