Triple
T6631998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladywell |
E149947
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Eliburn |
E143212
|
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: Eliburn | Statement: [Ladywell, locatedNear, Eliburn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eliburn Context triple: [Ladywell, locatedNear, Eliburn]
-
A.
Eliburn
chosen
Eliburn is a residential neighbourhood within the town of Livingston in West Lothian, Scotland.
-
B.
Thalgau
Thalgau is a municipality in the Austrian state of Salzburg, known for its scenic Alpine surroundings and proximity to the city of Salzburg.
-
C.
Elgol
Elgol is a small, scenic village on the Isle of Skye in Scotland, known for its dramatic coastal views and boat trips to the Cuillin mountains.
-
D.
Erigon
Erigon is a high-performance, modular Ethereum execution client focused on efficient resource usage and fast synchronization.
-
E.
Tynaarlo
Tynaarlo is a municipality in the northeastern Netherlands known for its rural character and location between the cities of Groningen and Assen.
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6afc9138c81909d228ce4936d6b8b |
completed | March 27, 2026, 4:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cbf329f08190a3f29c4d4c6aa136 |
completed | March 27, 2026, 6:26 p.m. |
Created at: March 27, 2026, 1:59 p.m.