Triple
T28878679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zana |
E732351
|
entity |
| Predicate | fosterChildOf |
P31761
|
FINISHED |
| Object | David Bryan |
—
|
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: David Bryan | Statement: [Zana, fosterChildOf, David Bryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fosterChildOf Context triple: [Zana, fosterChildOf, David Bryan]
-
A.
fosterChild
chosen
Indicates a relationship where one person is the child being cared for and raised by foster parents who are not their biological or legal parents.
-
B.
fosteredAt
Indicates that an entity is being or has been cared for or temporarily housed at a particular foster location or institution.
-
C.
entrustsChildTo
Indicates that one person or entity places a child under the care, supervision, or responsibility of another person or entity.
-
D.
fosterMother
Indicates a parental relationship where a woman temporarily cares for and raises a child who is not biologically her own, typically through a formal fostering arrangement.
-
E.
fosterSister
Indicates a sister relationship created through foster care rather than through birth or legal adoption.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4d874c819094de2d585e1f5816 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:40 a.m.