Triple
T15508743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calum MacLeod |
E368649
|
entity |
| Predicate | hasFamilyNameForm |
P27865
|
FINISHED |
| Object | MacLeod |
E74847
|
NE 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: MacLeod | Statement: [Calum MacLeod, hasFamilyNameForm, MacLeod]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MacLeod Context triple: [Calum MacLeod, hasFamilyNameForm, MacLeod]
-
A.
MacLeod
chosen
MacLeod is a Scottish surname historically associated with the Highlands and the Isle of Skye, borne by various notable figures in politics, arts, and public life.
-
B.
MacLamond
MacLamond is a Scottish surname associated as a sept with Clan Lamont, a historic Highland clan from Argyll.
-
C.
MacLachlin
MacLachlin is a Scottish surname associated as a sept with Clan MacLachlan of the Scottish Highlands.
-
D.
Loud MacLeod
Loud MacLeod is a famously bold and brightly colored Scottish tartan pattern associated with the MacLeod clan.
-
E.
Lochiel
Lochiel is the traditional title of the chief of Clan Cameron, a prominent Highland Scottish clan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03fd008708190a3657863eb9ac626 |
completed | April 16, 2026, 1:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff36702ebc81908d6a00243865de61 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 10, 2026, 3:55 a.m.