Triple
T38627346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridley family |
E937349
|
entity |
| Predicate | practicedCustom |
P191303
|
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: [Ridley family, practicedCustom, blood feud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practicedCustom Context triple: [Ridley family, practicedCustom, blood feud]
-
A.
practicedWith
Indicates that one entity engaged in practice or training together with another entity.
-
B.
practicedFor
Indicates that an entity engaged in preparation or rehearsal directed toward a particular event, activity, or objective.
-
C.
practicedOver
Indicates that one entity repeatedly or regularly performed an activity, skill, or behavior directed toward or involving another entity over a period of time.
-
D.
practicedUnder
Indicates that one entity gained experience or training while working under the guidance, supervision, or mentorship of another entity.
-
E.
practiseAs
Indicates that an entity performs or is engaged in a particular profession, role, or occupation in an official or recognized capacity.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.