Triple
T36534886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacNeacail |
E900547
|
entity |
| Predicate | historicalFeud |
P109978
|
FINISHED |
| Object | neighboring Highland clans |
—
|
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: neighboring Highland clans | Statement: [Clan MacNeacail, historicalFeud, neighboring Highland clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalFeud Context triple: [Clan MacNeacail, historicalFeud, neighboring Highland clans]
-
A.
feudedWith
chosen
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
B.
historicalEnemies
Indicates that the entities have been enemies of each other over a significant period in history.
-
C.
inspiredFeudWith
Indicates that one entity’s actions, ideas, or influence sparked or provoked a feud or ongoing conflict with another entity.
-
D.
hadFeudatory
Indicates that one entity served as a subordinate or vassal state under the authority or suzerainty of another entity.
-
E.
dynasticRival
Indicates a relationship in which two entities belong to competing ruling lineages or houses that contest power or succession against each other.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: May 3, 2026, 4:11 p.m.