Triple
T36909766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of Clan MacKenzie |
E912874
|
entity |
| Predicate | hasClanSeatHistorically |
P64286
|
FINISHED |
| Object | Eilean Donan 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: Eilean Donan Castle | Statement: [Chief of Clan MacKenzie, hasClanSeatHistorically, Eilean Donan Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanSeatHistorically Context triple: [Chief of Clan MacKenzie, hasClanSeatHistorically, Eilean Donan Castle]
-
A.
hasClanSeat
Indicates that an entity holds an official seat or position within a particular clan.
-
B.
hasHistoricClan
Indicates that an entity is associated with, or belongs to, a historically recognized clan or lineage group.
-
C.
hasHistoricalSeat
chosen
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
D.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
E.
hasClanChiefResidence
Indicates that a clan has the location where its chief resides or maintains an official dwelling.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:13 p.m.