Triple
T17536987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zernike Campus Groningen |
E427085
|
entity |
| Predicate | transportConnection |
P1298
|
FINISHED |
| Object | Groningen city bus network |
—
|
NE NERFINISHED |
How this triple was built (3 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: Groningen city bus network | Statement: [Zernike Campus Groningen, transportConnection, Groningen city bus network]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Groningen city bus network Context triple: [Zernike Campus Groningen, transportConnection, Groningen city bus network]
-
A.
Nijmegen city bus network
The Nijmegen city bus network is a public transportation system serving the city of Nijmegen and its surroundings, connecting key locations such as residential areas, the city center, and major institutions including the Heyendaal campus.
-
B.
The Hague bus network
The Hague bus network is the system of urban and regional bus routes serving The Hague and its surrounding areas, operated by the public transport company HTM.
-
C.
Rotterdam urban bus network
The Rotterdam urban bus network is the city’s primary system of local bus routes, providing extensive public transport coverage across Rotterdam and its surrounding areas.
-
D.
Utrecht bus network
The Utrecht bus network is the comprehensive system of urban and regional bus services that connects the city of Utrecht with its surrounding areas and key hubs.
-
E.
Amsterdam bus network
The Amsterdam bus network is an extensive public transportation system of urban and regional bus lines that connect neighborhoods, suburbs, and surrounding towns throughout the Amsterdam metropolitan area.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Groningen city bus network Target entity description: The Groningen city bus network is the primary public transportation system in and around the city of Groningen, providing frequent urban and regional bus services that connect key destinations such as residential areas, the city center, and major institutions.
-
A.
Nijmegen city bus network
The Nijmegen city bus network is a public transportation system serving the city of Nijmegen and its surroundings, connecting key locations such as residential areas, the city center, and major institutions including the Heyendaal campus.
-
B.
The Hague bus network
The Hague bus network is the system of urban and regional bus routes serving The Hague and its surrounding areas, operated by the public transport company HTM.
-
C.
Rotterdam urban bus network
The Rotterdam urban bus network is the city’s primary system of local bus routes, providing extensive public transport coverage across Rotterdam and its surrounding areas.
-
D.
Utrecht bus network
The Utrecht bus network is the comprehensive system of urban and regional bus services that connects the city of Utrecht with its surrounding areas and key hubs.
-
E.
Amsterdam bus network
The Amsterdam bus network is an extensive public transportation system of urban and regional bus lines that connect neighborhoods, suburbs, and surrounding towns throughout the Amsterdam metropolitan area.
- F. None of above. chosen
Provenance (2 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4536d03dc81908b8a58f66657c01a |
completed | April 19, 2026, 4 a.m. |
Created at: April 10, 2026, 5:49 a.m.