Triple
T13533239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Ives Bridge |
E323188
|
entity |
| Predicate | hasBuildingInMiddle |
P14728
|
FINISHED |
| Object | bridge chapel in midstream |
—
|
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: bridge chapel in midstream | Statement: [St Ives Bridge, hasBuildingInMiddle, bridge chapel in midstream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingInMiddle Context triple: [St Ives Bridge, hasBuildingInMiddle, bridge chapel in midstream]
-
A.
containsBuilding
chosen
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
C.
hasBuildingLocation
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
D.
hasBuildingUnderCare
Indicates that an entity is responsible for the maintenance, management, or oversight of a particular building.
-
E.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbb34548190a6b44faa48125cd4 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.