Triple
T32171418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Despot of Epirus |
E821716
|
entity |
| Predicate | hasNeighboringPolity |
P46464
|
FINISHED |
| Object | Empire of Nicaea |
—
|
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: Empire of Nicaea | Statement: [Despot of Epirus, hasNeighboringPolity, Empire of Nicaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringPolity Context triple: [Despot of Epirus, hasNeighboringPolity, Empire of Nicaea]
-
A.
geopoliticalNeighbors
Indicates that two geopolitical entities share a common border or are directly adjacent to each other territorially.
-
B.
neighboringPolitiesHistorically
chosen
Indicates that two polities were geographically adjacent or shared a border during some historical period.
-
C.
hasFriendshipPactWith
Indicates a mutual agreement or bond of friendship established between two entities.
-
D.
vassalOrAllyOf
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
-
E.
hasNeighboringExclave
Indicates that one entity possesses an exclave that directly borders or is adjacent to an exclave of another entity.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 1, 2026, 12:33 a.m.