Triple
T14664911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacEwen |
E344341
|
entity |
| Predicate | associatedSurname |
P49952
|
FINISHED |
| Object | MacEwan |
E891359
|
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: MacEwan | Statement: [Clan MacEwen, associatedSurname, MacEwan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MacEwan Context triple: [Clan MacEwen, associatedSurname, MacEwan]
-
A.
MacEwan
chosen
MacEwan is a variant spelling of the Scottish surname McEwan, commonly associated with Scottish heritage and lineage.
-
B.
Kinnaird
Kinnaird is a historic Scottish estate and locality traditionally associated with the Carnegie family and the title of Lord Carnegie of Kinnaird.
-
C.
McKechnie
McKechnie is the Scottish-origin surname of American stage and film actress Florence Eldridge.
-
D.
MacLamond
MacLamond is a Scottish surname associated as a sept with Clan Lamont, a historic Highland clan from Argyll.
-
E.
Glen Huntly
Glen Huntly is a suburb in Melbourne, Australia, known for its residential character and access to public transport including tram services.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde177ced48190a448cbee1f4c75bf |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:27 a.m.