Triple
T27225378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glatt Valley |
E681395
|
entity |
| Predicate | nearbyMajorInfrastructure |
P136615
|
FINISHED |
| Object | Zurich Airport |
—
|
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: Zurich Airport | Statement: [Glatt Valley, nearbyMajorInfrastructure, Zurich Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMajorInfrastructure Context triple: [Glatt Valley, nearbyMajorInfrastructure, Zurich Airport]
-
A.
infrastructureNearby
chosen
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
B.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
C.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
-
D.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
E.
adjacentToInfrastructure
Indicates that one entity is located directly next to or in immediate proximity to a piece of infrastructure.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 9:44 a.m.