Triple
T14190388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacNaughton |
E351695
|
entity |
| Predicate | hasSept |
P60340
|
FINISHED |
| Object | MacNaughtan |
E865095
|
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: MacNaughtan | Statement: [Clan MacNaughton, hasSept, MacNaughtan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MacNaughtan Context triple: [Clan MacNaughton, hasSept, MacNaughtan]
-
A.
MacNiven
MacNiven is a surname, likely of Scottish origin, that serves as a variant form of the name Niven.
-
B.
MacMurrie
MacMurrie is a surname variant of Murray, a Scottish family name with Gaelic origins.
-
C.
MacRae
MacRae is a Scottish surname associated with various notable individuals in fields such as entertainment, sports, and public life.
-
D.
McNaughton
chosen
McNaughton is a Scottish-origin surname borne by various notable individuals in fields such as politics, the military, academia, and the arts.
-
E.
MacInness
MacInness is a Scottish surname associated as a sept with Clan MacInnes of the Scottish Highlands.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61df628c8190ba3f557e2128dce5 |
completed | April 14, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd280861fc81908c342fc229a526f3 |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 10, 2026, 1:03 a.m.