Triple
T31844273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cass and the Cassanovas |
E812892
|
entity |
| Predicate | hasRelativeOfMember |
P27845
|
FINISHED |
| Object | Johnny O’Keefe |
E1302585
|
NE 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: Johnny O’Keefe | Statement: [Cass and the Cassanovas, hasRelativeOfMember, Johnny O’Keefe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeOfMember Context triple: [Cass and the Cassanovas, hasRelativeOfMember, Johnny O’Keefe]
-
A.
hasRelativeActMember
Indicates that an entity has a relative who is a member of a specified act, group, or organization.
-
B.
hasRelativeRole
chosen
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
D.
hasMemberAlsoIn
Indicates that an entity has at least one member who also belongs to another specified group or collection.
-
E.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
- F. None of above.
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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01a819644c819094c58d083d525da0 |
completed | May 11, 2026, 9:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e65af59d8819085af3ed7782dabf2 |
completed | June 14, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_6a01a5dfd628819083c032d8cfd2e726 |
completed | May 11, 2026, 9:48 a.m. |
Created at: April 30, 2026, 11:50 p.m.