Triple
T20439390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John III of Trebizond |
E501341
|
entity |
| Predicate | realmLocatedOn |
P18608
|
FINISHED |
| Object | Black Sea coast |
—
|
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: Black Sea coast | Statement: [John III of Trebizond, realmLocatedOn, Black Sea coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmLocatedOn Context triple: [John III of Trebizond, realmLocatedOn, Black Sea coast]
-
A.
isLocatedOn
chosen
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
B.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
C.
regionSeatLocatedIn
Indicates that the administrative seat or capital of a region is located within that region.
-
D.
locationTerritory
Indicates that one entity is geographically or administratively situated within the territorial bounds or jurisdiction of another entity.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f112e48190a3af818c0f6ee839 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.