Triple
T37430248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurne Mouth |
E930113
|
entity |
| Predicate | hasNearbyWaterwayJunction |
P16534
|
FINISHED |
| Object | Thurne Dyke |
—
|
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: Thurne Dyke | Statement: [Thurne Mouth, hasNearbyWaterwayJunction, Thurne Dyke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWaterwayJunction Context triple: [Thurne Mouth, hasNearbyWaterwayJunction, Thurne Dyke]
-
A.
waterwayJunction
chosen
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
B.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
C.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
D.
nearbyInternationalWaterway
Indicates that one entity is located close to an international waterway, such as a river, canal, or sea route that crosses or borders multiple countries.
-
E.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 3, 2026, 4:17 p.m.