Triple
T30002217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Eavis |
E762199
|
entity |
| Predicate | hasChildCollaborator |
P191580
|
FINISHED |
| Object | Emily Eavis |
—
|
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: Emily Eavis | Statement: [Michael Eavis, hasChildCollaborator, Emily Eavis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildCollaborator Context triple: [Michael Eavis, hasChildCollaborator, Emily Eavis]
-
A.
hasChildCoauthor
Indicates that an entity has at least one child who is also a coauthor with that entity on a work or publication.
-
B.
hasSiblingCollaboration
Indicates a collaborative relationship between two entities that are considered siblings within the same hierarchy or family.
-
C.
hasTeamMember
Indicates that an entity includes another entity as a member of its team.
-
D.
hasLayCollaborators
Indicates that an entity is supported or assisted by non-professional or non-specialist collaborators in carrying out its activities or functions.
-
E.
hasSiblingMembers
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:41 p.m.