Triple
T35146978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latheron, Caithness |
E1014867
|
entity |
| Predicate | hasNearbyClanCentre |
P201529
|
FINISHED |
| Object | Clan Gunn Heritage Centre |
—
|
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: Clan Gunn Heritage Centre | Statement: [Latheron, Caithness, hasNearbyClanCentre, Clan Gunn Heritage Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyClanCentre Context triple: [Latheron, Caithness, hasNearbyClanCentre, Clan Gunn Heritage Centre]
-
A.
hasNearbyColony
Indicates that one entity has another entity located close enough to be considered a nearby colony.
-
B.
hasClanSeatWithin
Indicates that a clan’s designated seat, base, or stronghold is located within a specified area or jurisdiction.
-
C.
hasClanTerritory
Indicates that a clan possesses or controls a specific geographic territory as its domain.
-
D.
hasNearbyTribalLand
Indicates that an entity is located close to or adjacent to land officially recognized as belonging to a tribal nation or indigenous community.
-
E.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_6a000013004c8190a01710441f881fdc |
completed | May 10, 2026, 3:48 a.m. |
Created at: May 3, 2026, 4:02 p.m.