Triple
T17050843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speyside |
E413688
|
entity |
| Predicate | hasNotableTown |
P14082
|
FINISHED |
| Object | Rothes |
E584893
|
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: Rothes | Statement: [Speyside, hasNotableTown, Rothes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rothes Context triple: [Speyside, hasNotableTown, Rothes]
-
A.
Rothes
chosen
Rothes is a small Speyside town in Moray, Scotland, known for its whisky distilleries and location on the River Spey.
-
B.
Brunstane
Brunstane is a suburban area in the eastern part of Edinburgh, Scotland, known primarily as a residential district served by its local railway station.
-
C.
Foulis
Foulis is the traditional Highland estate and seat associated with Clan Munro in Scotland.
-
D.
Colquhoun
Colquhoun is a Scottish surname and Highland clan name historically associated with Clan Grant as one of its septs.
-
E.
Cromvoirt
Cromvoirt is a small village in the Dutch province of North Brabant, known for its rural character and proximity to the city of ’s-Hertogenbosch.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa26e84819098b41ae15618e813 |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012341b8e88190a2bee865be5ca1c1 |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.