Triple
T14731190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A79 road |
E346077
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Monkton |
E783666
|
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: Monkton | Statement: [A79 road, connects, Monkton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Monkton Context triple: [A79 road, connects, Monkton]
-
A.
Monkton
chosen
Monkton is a small village in South Ayrshire, Scotland, situated near Prestwick and close to the west coast.
-
B.
Nunton
Nunton is a small crofting settlement on the island of Benbecula in Scotland’s Outer Hebrides, known for its traditional landscape and historic township character.
-
C.
Tarrant Monkton
Tarrant Monkton is a small rural village in Dorset, England, known for its traditional countryside setting and historic parish church.
-
D.
Simington
Simington is a surname variant of Symington, typically of Scottish origin and associated with families from places bearing that name.
-
E.
Mottingham
Mottingham is a suburban district in southeast London, England, known for its residential character and green spaces.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26311c8819093a81ff0fa43b33b |
completed | April 14, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb89ea388190b356df74e36023f7 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.