Triple
T5402407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komárom-Esztergom County |
E120808
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Komárom |
E281398
|
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: Komárom | Statement: [Komárom-Esztergom County, contains, Komárom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Komárom Context triple: [Komárom-Esztergom County, contains, Komárom]
-
A.
Komárno
chosen
Komárno is a historic town and river port in southern Slovakia, situated at the confluence of the Danube and Váh rivers on the border with Hungary.
-
B.
Belá
Belá is a mountain river in northern Slovakia known for its clear waters, dynamic flow, and popularity among whitewater enthusiasts.
-
C.
Komló
Komló is a town in southern Hungary known historically for its coal mining and hop-growing industries.
-
D.
Sopron
Sopron is a historic city in western Hungary near the Austrian border, known for its well-preserved medieval old town and wine-making traditions.
-
E.
Kaposvár
Kaposvár is a city in southwestern Hungary that serves as the administrative and cultural center of Somogy County.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87731c1c81909a4dc865282bd289 |
completed | March 20, 2026, 5:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf7fd5099081908ace06c317f6afd1 |
completed | March 22, 2026, 5:36 a.m. |
Created at: March 20, 2026, 2:04 p.m.