Triple
T6883697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brda |
E158861
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Tuchola |
E705471
|
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: Tuchola | Statement: [Brda, passesNear, Tuchola]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tuchola Context triple: [Brda, passesNear, Tuchola]
-
A.
Tuchola
chosen
Tuchola is a town in northern Poland that lends its name to the surrounding Tuchola Forest, one of the largest forest complexes in the country.
-
B.
Chojnice
Chojnice is a historic town in northern Poland known for its medieval architecture and role as a local cultural and economic center.
-
C.
Muszyna
Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
-
D.
Wiślica
Wiślica is a historic town in south-central Poland, known for its medieval architecture and archaeological significance as one of the country’s oldest settlements.
-
E.
Łęczna
Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8ea59108190a85f9112b6a4e59a |
completed | March 27, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc60b0ae48190bb6e6f38bcbb05dd |
completed | April 2, 2026, 1:27 a.m. |
Created at: March 27, 2026, 2:23 p.m.