Triple
T5958848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotor region |
E132583
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Risan |
E481725
|
NE 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: Risan | Statement: [Kotor region, contains, Risan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Risan Context triple: [Kotor region, contains, Risan]
-
A.
Risan
chosen
Risan is a historic coastal town in Montenegro, situated along the Bay of Kotor and known for its ancient Illyrian and Roman heritage.
-
B.
Miyazya
Miyazya is one of the spring months in the Ethiopian calendar, roughly corresponding to April in the Gregorian calendar.
-
C.
Shiga
Shiga is a landlocked prefecture in central Japan known for encompassing Lake Biwa, the country’s largest freshwater lake, and for its historical sites and natural scenery.
-
D.
Kuwana
Kuwana is a city in central Japan known historically as a post town on the Tōkaidō route and for its cultural sites and traditional festivals.
-
E.
Settsu
Settsu is a city in Osaka Prefecture, Japan, known as part of the Osaka metropolitan area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c039c48d0c81908e794c52fddf2ca2 |
completed | March 22, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e3e3736c8190b445156f0c1bdf1f |
completed | March 23, 2026, 6:55 a.m. |
Created at: March 22, 2026, 4:02 p.m.