Triple
T17279525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodhouse Lane, Leeds |
E419484
|
entity |
| Predicate | nearbyOpenSpace |
P61270
|
FINISHED |
| Object | Woodhouse Moor vicinity |
—
|
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: Woodhouse Moor vicinity | Statement: [Woodhouse Lane, Leeds, nearbyOpenSpace, Woodhouse Moor vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyOpenSpace Context triple: [Woodhouse Lane, Leeds, nearbyOpenSpace, Woodhouse Moor vicinity]
-
A.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
B.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
-
C.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
D.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
E.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e433286f6c8190bf4a757707707e22 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.