Triple
T36750674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZL |
E907902
|
entity |
| Predicate | relatedCityCode |
—
|
GENERATED |
| Object | Zwolle |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCityCode Context triple: [ZL, relatedCityCode, Zwolle]
-
A.
associatedCityCode
Indicates that an entity is linked or related to a specific city identified by its code.
-
B.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
C.
linkedCityRegion
Indicates that a city is associated with, belongs to, or is administratively connected to a specific region.
-
D.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
E.
associatedCityState
Indicates a relationship where a city is linked to the state with which it is formally or contextually connected.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.