Triple
T37589998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titford Canal |
E935233
|
entity |
| Predicate | isUrbanCanal |
P41360
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Titford Canal, isUrbanCanal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanCanal Context triple: [Titford Canal, isUrbanCanal, true]
-
A.
isUrbanWaterway
chosen
Indicates that a waterway is located within, passes through, or primarily serves an urban or metropolitan area.
-
B.
isUrbanRiverOf
Indicates that a river flows through or is located within an urban area associated with a specified place or city.
-
C.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
D.
isUrbanWaterfront
Indicates that a location is situated along a body of water within an urban or metropolitan area.
-
E.
isUrbanLake
Indicates that a given lake is located within or closely associated with an urban or metropolitan area.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.