Triple
T19706709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iffley Lock |
E473233
|
entity |
| Predicate | hasNearbyFeature |
P350
|
FINISHED |
| Object | Iffley village |
—
|
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: Iffley village | Statement: [Iffley Lock, hasNearbyFeature, Iffley village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iffley village Context triple: [Iffley Lock, hasNearbyFeature, Iffley village]
-
A.
Iffley
chosen
Iffley is a historic village now part of Oxford, England, known for its Romanesque church and picturesque setting along the River Thames.
-
B.
Englefield Green
Englefield Green is a village in Surrey, England, known for its proximity to Runnymede and its large common land.
-
C.
Croxley Green
Croxley Green is a large village and residential suburb near Watford in southern England, known for its green spaces and commuter links to London.
-
D.
Tilford Green
Tilford Green is a central village green in Tilford, Surrey, known for its picturesque open space and traditional English rural character.
-
E.
Bletchingley
Bletchingley is a historic village in Surrey, England, known for its medieval origins and picturesque rural setting.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642bb5cd4819090e4c62bd74c4324 |
completed | April 20, 2026, 3:14 p.m. |
Created at: April 10, 2026, 1:46 p.m.