Triple
T33515035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagner family |
E858343
|
entity |
| Predicate | hasFamilyHeadRole |
P38221
|
FINISHED |
| Object | director of the Bayreuth Festival |
—
|
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: director of the Bayreuth Festival | Statement: [Wagner family, hasFamilyHeadRole, director of the Bayreuth Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyHeadRole Context triple: [Wagner family, hasFamilyHeadRole, director of the Bayreuth Festival]
-
A.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
B.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
D.
hasSpousePositionInFamily
Indicates that a person’s spouse holds a specific role or position within the family structure.
-
E.
hasFamilyOrganization
Indicates that an entity is associated with, belongs to, or is structured within a particular family-based organizational unit or system.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 1:39 a.m.