Triple
T17655336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuřim |
E429606
|
entity |
| Predicate | hasDistrictCodeLAU |
P43726
|
FINISHED |
| Object | CZ0642 |
—
|
LITERAL 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: CZ0642 | Statement: [Kuřim, hasDistrictCodeLAU, CZ0642]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistrictCodeLAU Context triple: [Kuřim, hasDistrictCodeLAU, CZ0642]
-
A.
hasLocalGovernmentAreaCode
Indicates that an entity is associated with a specific local government area identified by a particular code.
-
B.
districtCode
chosen
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
C.
localAuthorityDistrictCode
Indicates the specific local authority district to which an entity is administratively assigned, represented by its official code.
-
D.
hasLocalGovernmentCode
Indicates that an entity is associated with a specific code assigned by a local government authority for identification or administrative purposes.
-
E.
containsLocalAuthorityArea
Indicates that one entity geographically encompasses or includes the entire area governed by a specific local authority.
- F. None of above.
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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e40e344819086a49c69f8f2956b |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:06 a.m.