Triple
T34499536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CZ-KR |
E885708
|
entity |
| Predicate | neighboringSubdivisionCode |
P179659
|
FINISHED |
| Object | CZ-PA |
—
|
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: CZ-PA | Statement: [CZ-KR, neighboringSubdivisionCode, CZ-PA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringSubdivisionCode Context triple: [CZ-KR, neighboringSubdivisionCode, CZ-PA]
-
A.
subdivisionIdentifier
Indicates a relationship where a specific identifier is assigned to distinguish a particular subdivision within a larger entity or structure.
-
B.
localSubdivision
Indicates that one administrative or geographic area is a smaller, constituent part within a larger local jurisdiction or region.
-
C.
isSuburbanNeighborhoodOf
Indicates that one area is a residential neighborhood located within or characteristic of the suburbs of another, typically larger, urban area.
-
D.
subdivisionFlagOf
Indicates that one administrative or territorial unit is a designated subdivision or sub-part of another unit.
-
E.
isLocatedInSubdivision
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
- F. None of above. chosen
Provenance (4 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:01 a.m.