Triple
T35315119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of Clan Donnachaidh |
E1019881
|
entity |
| Predicate | clanRegion |
P129330
|
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: [Chief of Clan Donnachaidh, clanRegion, Scottish Highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanRegion Context triple: [Chief of Clan Donnachaidh, clanRegion, Scottish Highlands]
-
A.
clanDistrict
chosen
Indicates that a clan is associated with, based in, or traditionally linked to a particular district.
-
B.
clanOrKingdom
Indicates a relationship where an entity is associated with, belongs to, or is part of a particular clan or kingdom.
-
C.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
-
D.
tribeInheritanceRegion
Indicates the geographic region or area from which a tribe’s inheritance, territory, or ancestral land is derived or associated.
-
E.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79090c29c81909172903f1c5d82c8 |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.