Triple
T18193369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilla Edet |
E435597
|
entity |
| Predicate | hasRiverRelatedInfrastructure |
P44836
|
FINISHED |
| Object | canal locks |
—
|
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: canal locks | Statement: [Lilla Edet, hasRiverRelatedInfrastructure, canal locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverRelatedInfrastructure Context triple: [Lilla Edet, hasRiverRelatedInfrastructure, canal locks]
-
A.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasRiverInfluence
Indicates that one entity affects or is affected by a river in terms of its characteristics, behavior, or conditions.
-
D.
associatedWithWaterways
chosen
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
E.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d12b688190842375dcc5d5537c |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.