Triple
T30776234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lendalfoot |
E783677
|
entity |
| Predicate | hasScottishRegion |
P285
|
FINISHED |
| Object | South Scotland electoral region |
—
|
NE NERFINISHED |
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: South Scotland electoral region | Statement: [Lendalfoot, hasScottishRegion, South Scotland electoral region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScottishRegion Context triple: [Lendalfoot, hasScottishRegion, South Scotland electoral region]
-
A.
hasCapitalCityOfScotland
Indicates the relationship in which an entity has, as its capital city, the city that serves as the capital of Scotland.
-
B.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
hasNameInScots
Indicates that an entity has a specific name or designation expressed in the Scots language.
-
D.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
E.
isInHighlandRegion
Indicates that an entity is located within a highland or elevated geographic region.
- F. None of above.
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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 8:40 p.m.