Triple
T13880387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River North Esk |
E333696
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Edzell |
E101550
|
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: Edzell | Statement: [River North Esk, flowsNear, Edzell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edzell Context triple: [River North Esk, flowsNear, Edzell]
-
A.
Edzell
chosen
Edzell is a small historic village in Angus, Scotland, known for its picturesque setting, nearby glens, and the ruins of Edzell Castle.
-
B.
Gavinton
Gavinton is a small village in the Scottish Borders region of Scotland, situated near the town of Duns.
-
C.
Fairburn
Fairburn is a small suburban city in Fulton County, Georgia, that forms part of the greater Atlanta metropolitan area.
-
D.
Kincorth
Kincorth is a residential area in the south of Aberdeen, Scotland, known for its post-war housing and proximity to the River Dee.
-
E.
Harput
Harput is an ancient settlement and archaeological site in eastern Turkey known for its historic fortress, churches, and layered cultural heritage spanning multiple civilizations.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0be8566881908b8902e3cd567669 |
completed | April 14, 2026, 9:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c711f9b08190aa5981320597e83b |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:15 p.m.