Triple
T15592353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Johnstone |
E374775
|
entity |
| Predicate | feudType |
P119353
|
FINISHED |
| Object | blood 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: blood feud | Statement: [Clan Johnstone, feudType, blood feud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudType Context triple: [Clan Johnstone, feudType, blood feud]
-
A.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
B.
feudalFunction
Indicates the role or duty an entity holds within a feudal hierarchy, such as obligations, services, or functions owed to or performed for another.
-
C.
feudalRights
Indicates that one party holds traditional feudal privileges, claims, or entitlements over another party or resource within a hierarchical lord–vassal structure.
-
D.
isFeudal
Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
-
E.
typeOfFeudalGrant
Indicates the specific kind or category of feudal grant that characterizes the relationship between a grantor and a grantee within a feudal system.
- F. None of above. chosen
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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e5e43d48190a8fd367f13f1c7e1 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.