Triple
T36750674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZL |
E907902
|
entity |
| Predicate | relatedCityCode |
P205032
|
FINISHED |
| Object | Zwolle |
E353304
|
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: Zwolle | Statement: [ZL, relatedCityCode, Zwolle]
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 (5 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7c3cb7369081908b3049d5a6e2fcac |
completed | Aug. 12, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.