Triple
T4931885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macclesfield Canal |
E110714
|
entity |
| Predicate | hasMaximumBoatBeam |
P12550
|
FINISHED |
| Object | narrowboat |
—
|
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: narrowboat | Statement: [Macclesfield Canal, hasMaximumBoatBeam, narrowboat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumBoatBeam Context triple: [Macclesfield Canal, hasMaximumBoatBeam, narrowboat]
-
A.
maximumShipBeam
chosen
Indicates the greatest allowable or observed width of a ship across its widest point.
-
B.
hasBerthDepth
Indicates the depth of water available at a specific berth where a vessel can be moored.
-
C.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
-
D.
maximumVesselDraft
Indicates the greatest depth a vessel can safely extend below the waterline, typically limiting where it can navigate or dock.
-
E.
maximumVesselLength
Indicates the greatest allowable or observed length of a vessel in a given context or constraint.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7063c57c8190a5a6fb3586238d35 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.