Triple
T33427232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverness-shire County Council |
E856018
|
entity |
| Predicate | governedAreaIncludes |
P11585
|
FINISHED |
| Object | Inverness |
—
|
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: Inverness | Statement: [Inverness-shire County Council, governedAreaIncludes, Inverness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedAreaIncludes Context triple: [Inverness-shire County Council, governedAreaIncludes, Inverness]
-
A.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
B.
governanceArea
chosen
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
C.
governsAreaKnownFor
Indicates that a governing entity exercises authority over an area that is notably recognized for a particular characteristic, feature, or attribute.
-
D.
culturalAreaIncludes
Indicates that a broader cultural area encompasses or contains a smaller cultural region or entity within its scope.
-
E.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:36 a.m.