Triple
T26395938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirknewton and East Calder |
E663554
|
entity |
| Predicate | hasPrimaryVillages |
P191337
|
FINISHED |
| Object | Kirknewton |
—
|
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: Kirknewton | Statement: [Kirknewton and East Calder, hasPrimaryVillages, Kirknewton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryVillages Context triple: [Kirknewton and East Calder, hasPrimaryVillages, Kirknewton]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
hasPopularVillage
Indicates that an entity is associated with or contains a village that is widely known, well-liked, or frequently visited.
-
C.
hasVillageAtHead
Indicates that a village is located at the head (source or upper end) of a geographic feature such as a valley, river, or bay.
-
D.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
-
E.
hasVillageCluster
Indicates that one entity contains, is associated with, or is organized into a specific cluster or grouping of villages.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 26, 2026, 11:28 p.m.