Triple
T9389708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burscough |
E225993
|
entity |
| Predicate | hasCanalsideSetting |
P88667
|
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: [Burscough, hasCanalsideSetting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanalsideSetting Context triple: [Burscough, hasCanalsideSetting, true]
-
A.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
B.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
C.
hasCanalSection
Indicates a relationship where one entity includes, contains, or is associated with a specific section or segment of a canal.
-
D.
hasSeasideSetting
Indicates that something is situated in, near, or directly overlooking the sea or seashore.
-
E.
hasCanalLock
Indicates that one entity (typically a canal or waterway) includes or is equipped with a canal lock used to raise and lower boats between stretches of water at different levels.
- F. None of above. chosen
Provenance (4 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d83c188190925c389dff1341b0 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:45 p.m.