Triple
T13022611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Gunn |
E326212
|
entity |
| Predicate | notableFeud |
P22787
|
FINISHED |
| Object | Clan Gunn–Clan Keith feud |
—
|
LITERAL 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: Clan Gunn–Clan Keith feud | Statement: [Clan Gunn, notableFeud, Clan Gunn–Clan Keith feud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeud Context triple: [Clan Gunn, notableFeud, Clan Gunn–Clan Keith feud]
-
A.
inspiredFeudWith
Indicates that one entity’s actions, ideas, or influence sparked or provoked a feud or ongoing conflict with another entity.
-
B.
notableFamilyConflict
Indicates a significant, recognized dispute or ongoing tension between members of the same family.
-
C.
notableConflictWith
chosen
Indicates a significant, recognized conflict or dispute that exists or has existed between the related entities.
-
D.
notableInternalConflict
Indicates a significant or historically important internal conflict occurring within an entity, such as a country, organization, or group.
-
E.
firstHolderNotableConflict
Indicates that the first holder of a position, title, or role is associated with a notable conflict, dispute, or controversy.
- F. None of above.
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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ed05e9c8190a4f208662bca0602 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:52 p.m.