Triple
T22145590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogielica |
E547278
|
entity |
| Predicate | nearbyTown |
P3883
|
FINISHED |
| Object | Dobra |
—
|
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: Dobra | Statement: [Mogielica, nearbyTown, Dobra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dobra Context triple: [Mogielica, nearbyTown, Dobra]
-
A.
Dobra
Dobra is a river in central Croatia known for flowing through Karlovac County and contributing to the region’s karst landscape and hydropower resources.
-
B.
Dobra
chosen
Dobra is a village in southern Poland, known as a base for hiking in the Beskid Wyspowy mountains, including nearby peaks like Ćwilin.
-
C.
dobra
The dobra is the official monetary unit of São Tomé and Príncipe, a small island nation off the west coast of Central Africa.
-
D.
Dobrada
Dobrada is a small municipality in the state of São Paulo, Brazil, known for its agricultural economy and rural character.
-
E.
Dobrota
Dobrota is a coastal town in Montenegro known for its historic stone houses and scenic waterfront along the Bay of Kotor.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f097248190a8a3cdff1593b5b5 |
completed | April 28, 2026, 9:43 p.m. |
Created at: April 16, 2026, 8:33 p.m.