Triple
T12529619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacInnes |
E299525
|
entity |
| Predicate | hasSurnameForm |
P18
|
FINISHED |
| Object | MacInness |
E986222
|
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: MacInness | Statement: [Clan MacInnes, hasSurnameForm, MacInness]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MacInness Context triple: [Clan MacInnes, hasSurnameForm, MacInness]
-
A.
MacInness
chosen
MacInness is a Scottish surname associated as a sept with Clan MacInnes of the Scottish Highlands.
-
B.
MacNiven
MacNiven is a surname, likely of Scottish origin, that serves as a variant form of the name Niven.
-
C.
MacInnis
MacInnis is a Scottish surname associated with Clan MacInnes, a Highland clan with historical roots in the western coastal regions of Scotland.
-
D.
MacRae
MacRae is a Scottish surname associated with various notable individuals in fields such as entertainment, sports, and public life.
-
E.
McInness
McInness is a Scottish surname associated with Clan MacInnes, a Highland clan of ancient origin.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95469d100819087c83bc55e3ec9ce |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65eae71fc819083ec63dbfbf32465 |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 9:57 p.m.