Triple
T33645633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodarte |
E861952
|
entity |
| Predicate | founderSiblingRelationship |
P132967
|
FINISHED |
| Object | Kate and Laura Mulleavy are sisters |
—
|
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: Kate and Laura Mulleavy are sisters | Statement: [Rodarte, founderSiblingRelationship, Kate and Laura Mulleavy are sisters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderSiblingRelationship Context triple: [Rodarte, founderSiblingRelationship, Kate and Laura Mulleavy are sisters]
-
A.
founderRelation
Indicates that one entity is the founder or creator of another entity, such as an organization, project, or initiative.
-
B.
siblingOrRelative
chosen
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
C.
hasFounderRelationship
Indicates a relationship where one entity serves as the founder or co-founder of another entity.
-
D.
parentOfFounder
Indicates that one entity is the parent of another entity who is the founder of something (such as an organization, company, or project).
-
E.
spouseOfSiblingOf
Indicates the person who is married to someone’s sibling.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 1, 2026, 1:42 a.m.