Triple
T32573613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldon Canal |
E832580
|
entity |
| Predicate | FroghallTunnelCharacteristic |
P174609
|
FINISHED |
| Object | low headroom |
—
|
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: low headroom | Statement: [Caldon Canal, FroghallTunnelCharacteristic, low headroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FroghallTunnelCharacteristic Context triple: [Caldon Canal, FroghallTunnelCharacteristic, low headroom]
-
A.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
B.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
-
C.
tunnelDugBy
Indicates that a tunnel was created or excavated by a particular agent or entity.
-
D.
hasRockTunnel
Indicates that one entity possesses, contains, or provides access to a tunnel that passes through rock.
-
E.
lengthOfTunnels
Indicates the measured extent or distance of tunnels associated with an entity.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63ca2e881909f8e056c1ed181ba |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:04 a.m.