Triple
T26423319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farlington |
E664299
|
entity |
| Predicate | waterProximity |
P8567
|
FINISHED |
| Object | near River Foss |
—
|
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: near River Foss | Statement: [Farlington, waterProximity, near River Foss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterProximity Context triple: [Farlington, waterProximity, near River Foss]
-
A.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
B.
waterBodyCreatedNearby
Indicates that a water body has been formed or established in close spatial proximity to a specified reference location or entity.
-
C.
waterPresence
Indicates the existence or amount of water present in or around a specified entity or location.
-
D.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
-
E.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 11:44 p.m.