Triple
T38429278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Aird of Lovat |
E903752
|
entity |
| Predicate | associatedClanTitle |
P23606
|
FINISHED |
| Object | Lord Lovat |
E2272402
|
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: Lord Lovat | Statement: [The Aird of Lovat, associatedClanTitle, Lord Lovat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedClanTitle Context triple: [The Aird of Lovat, associatedClanTitle, Lord Lovat]
-
A.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
B.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
-
C.
clanNameBeforeTitle
Indicates that a clan name is placed before a person’s title in the full expression of their name.
-
D.
clanChiefTitleOf
chosen
Indicates that one entity is the formal title held by the chief or leader of a particular clan.
-
E.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
- F. None of above.
Provenance (4 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e0170b7c8190bb4881465734bbe1 |
completed | June 29, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.