Triple
T20500597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İnceburun Lighthouse |
E503289
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | city of Sinop |
—
|
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: city of Sinop | Statement: [İnceburun Lighthouse, locatedNear, city of Sinop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Sinop Context triple: [İnceburun Lighthouse, locatedNear, city of Sinop]
-
A.
Sinop
chosen
Sinop is a historic port city on Turkey’s Black Sea coast, long valued for its strategic harbor and role in regional trade and defense.
-
B.
Sinop
Sinop is a major agricultural and commercial city in the northern region of the Brazilian state of Mato Grosso.
-
C.
Pavlograd
Pavlograd is a city in eastern Ukraine known historically as a regional industrial and transport center in the Dnipropetrovsk area.
-
D.
Petrovgrad
Petrovgrad was the former name of the Serbian city now known as Zrenjanin, located in the Vojvodina region.
-
E.
Sevastopol
Sevastopol is a major port city on the Black Sea, historically significant as a naval base and the site of key military conflicts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cc1ea7081908d17c224b1670bd7 |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.