Triple
T29799986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgar Ravenswood |
E756664
|
entity |
| Predicate | hasFamilyFeudWith |
P183118
|
FINISHED |
| Object | Ashton family |
—
|
NE NERFINISHED |
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: Ashton family | Statement: [Edgar Ravenswood, hasFamilyFeudWith, Ashton family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyFeudWith Context triple: [Edgar Ravenswood, hasFamilyFeudWith, Ashton family]
-
A.
hasFamilyProgram
Indicates that an entity offers or is associated with a program specifically designed for families.
-
B.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
C.
hasFamilyFriend
Indicates that one entity has another entity as a friend who is connected through family ties or close familial relationships.
-
D.
isFromFamilyKnownFor
Indicates that an entity belongs to a family that is widely recognized or notable for a particular characteristic, achievement, or reputation.
-
E.
hasPerformerFamily
Indicates that an entity has a family member who performs or participates as a performer in relation to that entity.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 29, 2026, 5:17 p.m.