Triple
T28365578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil’s Bridge, Kirkby Lonsdale |
E718475
|
entity |
| Predicate | hasSideArchSpan |
P26118
|
FINISHED |
| Object | about 9 metres each |
—
|
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: about 9 metres each | Statement: [Devil’s Bridge, Kirkby Lonsdale, hasSideArchSpan, about 9 metres each]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideArchSpan Context triple: [Devil’s Bridge, Kirkby Lonsdale, hasSideArchSpan, about 9 metres each]
-
A.
hasSideArch
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
B.
sideArchWidth
chosen
Indicates the width measurement of a side arch in a structure or object.
-
C.
sideArchHeight
Indicates the vertical height measurement of a side arch relative to a reference point or baseline.
-
D.
hasNumberOfArches
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
E.
sideArchType
Indicates the architectural style or structural type used for the side arches in a construction or design.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 12:54 a.m.