Triple
T13064520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Lamont |
E329284
|
entity |
| Predicate | hasSept |
P60340
|
FINISHED |
| Object | MacLymont |
E1019056
|
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: MacLymont | Statement: [Clan Lamont, hasSept, MacLymont]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MacLymont Context triple: [Clan Lamont, hasSept, MacLymont]
-
A.
MacClymont
chosen
MacClymont is a Scottish surname associated as a sept with Clan Lamont, a historic Highland clan from Argyll.
-
B.
Moncrieff
Moncrieff is a residential suburb in the Gungahlin district of Canberra, Australian Capital Territory.
-
C.
MacLamond
MacLamond is a Scottish surname associated as a sept with Clan Lamont, a historic Highland clan from Argyll.
-
D.
Lawmond
Lawmond is a Scottish family name recognized as a sept of Clan Lamont, a historic Highland clan from Argyll.
-
E.
Luncarty
Luncarty is a village in Perth and Kinross, Scotland, known historically for its linen bleaching industry and its proximity to the River Tay.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980e9bdfc81908eb90fb50597df64 |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d6016984819097c999772db1e831 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:59 p.m.