Triple
T6540081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wetherby |
E168262
|
entity |
| Predicate | bridgeStatus |
P72280
|
FINISHED |
| Object | Grade II listed structure |
—
|
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: Grade II listed structure | Statement: [Wetherby, bridgeStatus, Grade II listed structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeStatus Context triple: [Wetherby, bridgeStatus, Grade II listed structure]
-
A.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
B.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
C.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
D.
bridgePosition
Indicates the spatial or structural position of a bridge relative to other referenced elements or locations.
-
E.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6ce0538f48190abf3160681901c17 |
completed | March 27, 2026, 6:35 p.m. |
Created at: March 27, 2026, 1:50 p.m.