Triple
T23582980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innes |
E582257
|
entity |
| Predicate | traditionalLanguageCommunity |
P5562
|
FINISHED |
| Object | Scottish Highlands |
—
|
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: Scottish Highlands | Statement: [Innes, traditionalLanguageCommunity, Scottish Highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLanguageCommunity Context triple: [Innes, traditionalLanguageCommunity, Scottish Highlands]
-
A.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
B.
ethnicCommunityBase
Indicates that an ethnic community is based in, originates from, or is primarily associated with a particular place or area.
-
C.
ethnicCommunityContext
Indicates the cultural, social, or historical context related to an entity’s association with a particular ethnic community.
-
D.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
E.
languageFamilyTraditional
Indicates that one entity belongs to, or is classified under, the traditional language family of the other entity.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02e19808190a41bce305f6cd5da |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.