Triple
T11946117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutelo |
E284301
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Banski Suhodol |
E284302
|
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: Banski Suhodol | Statement: [Kutelo, hasViewOf, Banski Suhodol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Banski Suhodol Context triple: [Kutelo, hasViewOf, Banski Suhodol]
-
A.
Banski Suhodol
chosen
Banski Suhodol is a prominent high-altitude peak in Bulgaria’s Pirin mountain range, known for its rugged terrain and alpine scenery.
-
B.
Oreshek
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
-
C.
Vasishka
Vasishka was a Kushan emperor who ruled parts of northern India and Central Asia in the early 3rd century CE, known primarily from his inscriptions and coinage.
-
D.
Veliki Borak
Veliki Borak is a village located within the Barajevo municipality in the wider Belgrade region of Serbia.
-
E.
Vaskina
Vaskina is a small settlement located in the traditional Tsakonian region of the eastern Peloponnese in Greece.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903456ec0819082b8b10755a6b732 |
completed | April 10, 2026, 2:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f458cbb08881909a71f0592c9231ae |
completed | May 1, 2026, 7:39 a.m. |
Created at: April 8, 2026, 9:45 p.m.