Triple
T23458758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brühl, Germany |
E568006
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Kunice |
—
|
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: Kunice | Statement: [Brühl, Germany, twinTown, Kunice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kunice Context triple: [Brühl, Germany, twinTown, Kunice]
-
A.
Kunice
chosen
Kunice is a village in western Poland that forms part of the rural administrative district of Gmina Słubice in Lubusz Voivodeship.
-
B.
Junikowo
Junikowo is a residential district of Poznań in western Poland, known for its housing estates and local transport links.
-
C.
Koshice
Košice is the second-largest city in Slovakia, known for its well-preserved medieval old town and status as an important cultural and economic center in the country.
-
D.
Kamenka
Kamenka is a rural settlement located along the Mezen River in northern European Russia.
-
E.
Kokni
Kokni is an Indo-Aryan language spoken primarily by the Kokni tribal community in parts of western India, including Maharashtra and neighboring regions.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a699c0088190a84d7a495a3e3d61 |
completed | April 29, 2026, 6:35 a.m. |
Created at: April 17, 2026, 5:53 p.m.