Triple
T34339351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson Phillips |
E881242
|
entity |
| Predicate | hasParentOfMember |
P94756
|
FINISHED |
| Object | Brian Wilson |
—
|
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: Brian Wilson | Statement: [Wilson Phillips, hasParentOfMember, Brian Wilson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentOfMember Context triple: [Wilson Phillips, hasParentOfMember, Brian Wilson]
-
A.
hasMemberFather
chosen
Indicates that an entity is a member of a group or organization by virtue of their father’s membership or paternal relationship.
-
B.
isParentOf
Indicates that one entity is the biological or legal parent of another entity.
-
C.
hasSiblingMembers
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
D.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
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 (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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 1, 2026, 1:58 a.m.