Triple
T22735559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giethoorn |
E562259
|
entity |
| Predicate | waterwaysUsedFor |
P30340
|
FINISHED |
| Object | local transport |
—
|
LITERAL 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: local transport | Statement: [Giethoorn, waterwaysUsedFor, local transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwaysUsedFor Context triple: [Giethoorn, waterwaysUsedFor, local transport]
-
A.
waterwayFunction
chosen
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
D.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
E.
primaryWaterways
Indicates that the related entities are connected through major or principal bodies of water, such as main rivers, canals, or shipping routes that serve as key waterways between them.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1796f030881908e141564d442bd1b |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:22 p.m.