Triple
T17199404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elfstedentocht skating tour |
E417437
|
entity |
| Predicate | provinceCapitalOnRoute |
P65699
|
FINISHED |
| Object | Leeuwarden |
—
|
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: Leeuwarden | Statement: [Elfstedentocht skating tour, provinceCapitalOnRoute, Leeuwarden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceCapitalOnRoute Context triple: [Elfstedentocht skating tour, provinceCapitalOnRoute, Leeuwarden]
-
A.
countryCapitalTraversed
Indicates that a path, route, or traversal passes through the capital city of a specified country.
-
B.
provinceCapitalLocatedOn
Indicates that the capital of a province is geographically situated on or alongside a specified physical feature or location (such as a river, coast, or lake).
-
C.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
D.
provinceHeadquarters
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other entity.
-
E.
hasMajorCityOnRoute
chosen
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daddcd08190a82f36c940bf3f7b |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.