Triple
T26417746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flynn Bloom |
E664143
|
entity |
| Predicate | paternalHalfSibling |
P161007
|
FINISHED |
| Object | Daisy Dove Bloom |
—
|
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: Daisy Dove Bloom | Statement: [Flynn Bloom, paternalHalfSibling, Daisy Dove Bloom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalHalfSibling Context triple: [Flynn Bloom, paternalHalfSibling, Daisy Dove Bloom]
-
A.
hasHalfSibling
Indicates that two individuals share exactly one biological parent in common, making them half-siblings.
-
B.
hasHalfBrother
Indicates that one person has a male sibling with whom they share exactly one biological parent.
-
C.
paternalCousinOnceRemoved
Indicates a family relationship where one person is the child of another person's paternal cousin, or conversely, the paternal cousin of another person's parent.
-
D.
paternalAuntByMarriage
Indicates that one person is the wife of another person’s paternal uncle (their father’s brother).
-
E.
paternalNephewOf
Indicates that one person is the son of another person's brother (i.e., the nephew related through the father's side).
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61138a81c81908dbb9ad45436b3c1 |
completed | May 2, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 26, 2026, 11:41 p.m.