Triple
T17456952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal–Karst statistical region |
E425054
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sežana |
—
|
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: Sežana | Statement: [Coastal–Karst statistical region, contains, Sežana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sežana Context triple: [Coastal–Karst statistical region, contains, Sežana]
-
A.
Sežana
chosen
Sežana is a town in southwestern Slovenia near the Italian border, known as a regional center of the Karst area and an important transport and trade hub.
-
B.
Neša
Neša is the ancient name of the city of Kültepe, a major Bronze Age trading center and early Hittite capital in central Anatolia.
-
C.
Pavlina
Pavlina is a feminine given name, commonly used in Slavic countries as a variant of names like Paulina.
-
D.
Fažana
Fažana is a coastal town in Croatia’s Istria region, known for its fishing heritage, tourism, and historical ties to the Istriot language.
-
E.
Dáša
Dáša is a common Czech and Slovak feminine given name, typically used as a diminutive form of Dagmar.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45142b08481908cdd290692d796c3 |
completed | April 19, 2026, 3:51 a.m. |
Created at: April 10, 2026, 5:47 a.m.