Triple
T31440518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrenbury |
E802052
|
entity |
| Predicate | hasBridgeOnCanal |
P88936
|
FINISHED |
| Object | Wrenbury lift bridge |
—
|
NE NERFINISHED |
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: Wrenbury lift bridge | Statement: [Wrenbury, hasBridgeOnCanal, Wrenbury lift bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeOnCanal Context triple: [Wrenbury, hasBridgeOnCanal, Wrenbury lift bridge]
-
A.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
B.
hasDrawbridge
Indicates that one entity possesses or is equipped with a drawbridge as part of its structure or features.
-
C.
hasCanalCrossing
chosen
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
D.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
E.
hasFootbridge
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 9:05 p.m.