Triple
T28365577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil’s Bridge, Kirkby Lonsdale |
E718475
|
entity |
| Predicate | hasCentralArchSpan |
P37680
|
FINISHED |
| Object | about 16 metres |
—
|
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 16 metres | Statement: [Devil’s Bridge, Kirkby Lonsdale, hasCentralArchSpan, about 16 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralArchSpan Context triple: [Devil’s Bridge, Kirkby Lonsdale, hasCentralArchSpan, about 16 metres]
-
A.
centralArchWidth
chosen
Indicates the measured width of the central arch in a structure or object.
-
B.
hasNumberOfArches
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
C.
hasSideArch
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
D.
hasCentralBarStructure
Indicates that an object possesses a prominent elongated bar-like structure running through or near its center.
-
E.
hasCentralAxis
Indicates that one entity serves as the primary central axis or line of symmetry around which another entity is organized, aligned, or structured.
- 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_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 12:54 a.m.