Triple
T30747697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CZ071 |
E782858
|
entity |
| Predicate | adminCenterOfRepresentedRegion |
P117896
|
FINISHED |
| Object | Olomouc |
—
|
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: Olomouc | Statement: [CZ071, adminCenterOfRepresentedRegion, Olomouc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminCenterOfRepresentedRegion Context triple: [CZ071, adminCenterOfRepresentedRegion, Olomouc]
-
A.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
B.
adminCenterLocatedOn
Indicates that the administrative center of an entity is situated on or within a specified geographic or physical feature.
-
C.
representsAdministrativeRegion
Indicates that one entity serves as the administrative region or jurisdiction within which the other entity is governed or managed.
-
D.
administrativeCenterRegion
Indicates that a region serves as the administrative center or seat of government for another territorial unit.
-
E.
servesAsRegionalCenterFor
chosen
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 8:38 p.m.