Triple
T7739915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Yarrow |
E175479
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Yarrow village |
E685967
|
NE 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: Yarrow village | Statement: [River Yarrow, near, Yarrow village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yarrow village Context triple: [River Yarrow, near, Yarrow village]
-
A.
Yarrowford
chosen
Yarrowford is a small village in the Scottish Borders region of Scotland, situated in the Yarrow Valley near the River Yarrow.
-
B.
Laxfield
Laxfield is a historic rural village and civil parish in the English county of Suffolk, known for its traditional architecture and agricultural surroundings.
-
C.
Aherlow village
Aherlow village is a small rural settlement in Ireland situated in the scenic Glen of Aherlow at the foot of the Galtee Mountains.
-
D.
Atsion Village
Atsion Village is a historic 19th-century iron-making and later recreational community located within New Jersey’s Wharton State Forest in the Pine Barrens.
-
E.
Roan village
Roan village is a small coastal settlement in the Fosen region of Trøndelag county, Norway, known for its fishing heritage and scenic fjord landscape.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7035cddb881908bdfc1bd7d6a64ad |
completed | March 27, 2026, 10:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8c7c4482881908f7e763f019358cc |
completed | March 29, 2026, 6:33 a.m. |
Created at: March 27, 2026, 4:07 p.m.