Triple
T15542100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclean of Kingairloch |
E370503
|
entity |
| Predicate | hasClanWarCry |
P10430
|
FINISHED |
| Object | Bàs no Beatha (via Clan Maclean) |
—
|
LITERAL FINISHED |
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: Bàs no Beatha (via Clan Maclean) | Statement: [Maclean of Kingairloch, hasClanWarCry, Bàs no Beatha (via Clan Maclean)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanWarCry Context triple: [Maclean of Kingairloch, hasClanWarCry, Bàs no Beatha (via Clan Maclean)]
-
A.
hasClanName
Indicates that an entity bears or is associated with a particular clan name.
-
B.
warCry
chosen
Indicates a relationship where an entity utters or performs a loud, rallying shout or chant intended to inspire allies or intimidate opponents, typically in a conflict or competitive context.
-
C.
clanSlogan
Indicates the motto or slogan associated with a particular clan.
-
D.
hasClanSymbol
Indicates that an entity is associated with a particular clan through a specific identifying symbol.
-
E.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04432c3808190bb5b653bf8de30c6 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.