Triple
T36066828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of Clan Ross |
E1043254
|
entity |
| Predicate | historicalClanSeat |
P146715
|
FINISHED |
| Object | Balnagown Castle |
—
|
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: Balnagown Castle | Statement: [Chief of Clan Ross, historicalClanSeat, Balnagown Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalClanSeat Context triple: [Chief of Clan Ross, historicalClanSeat, Balnagown Castle]
-
A.
familySeatHistorically
chosen
Indicates that a particular location historically served as the principal residence or ancestral seat of a specific family or lineage.
-
B.
notableClans
Indicates that there exists a significant or historically important clan associated with the subject.
-
C.
hasHistoricClan
Indicates that an entity is associated with, or belongs to, a historically recognized clan or lineage group.
-
D.
isSeatOfInfluentialClan
Indicates that a location serves as the primary base or stronghold of a powerful or influential clan.
-
E.
clanSeatRelation
Indicates a relationship where a clan holds, occupies, or is associated with a particular seat, position, or place of authority.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:08 p.m.