Triple
T32103457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Leven |
E819915
|
entity |
| Predicate | hasVillageAtHead |
P190506
|
FINISHED |
| Object | Kinlochleven |
—
|
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: Kinlochleven | Statement: [Glen Leven, hasVillageAtHead, Kinlochleven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillageAtHead Context triple: [Glen Leven, hasVillageAtHead, Kinlochleven]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
hasVillageAtExit
Indicates that a village is located at or directly adjacent to an exit (such as a road, highway, or route exit).
-
C.
isVillageCenterOf
Indicates that a location functions as the central or main hub area of a specified village.
-
D.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
E.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
- F. None of above. chosen
Provenance (4 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 1, 2026, 12:26 a.m.