Triple
T21931794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stechford |
E541582
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Yardley |
—
|
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: Yardley | Statement: [Stechford, near, Yardley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yardley Context triple: [Stechford, near, Yardley]
-
A.
Yardley
chosen
Yardley is a suburban area of Birmingham, England, known for its historic village core and preserved Tudor-era buildings.
-
B.
Milldown
Milldown is a notable summit in the Rhinns of Kells range in the Galloway Hills of southwest Scotland, popular with hillwalkers for its rounded grassy slopes and expansive views.
-
C.
Rowley
Rowley is a small historic town in northeastern Massachusetts known for its colonial heritage and rural New England character.
-
D.
Rowley
Rowley is a surname of English origin borne by various notable individuals across fields such as politics, science, and the arts.
-
E.
Purleigh
Purleigh is a rural village and civil parish in Essex, England, known for its historic church, countryside setting, and traditional English character.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123ffde64819084a869d2d569718f |
completed | April 28, 2026, 9:17 p.m. |
Created at: April 16, 2026, 7:47 p.m.