Triple
T36111570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sybbie Branson |
E1044511
|
entity |
| Predicate | guardianAfterMothersDeath |
P175491
|
FINISHED |
| Object | Tom Branson |
—
|
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: Tom Branson | Statement: [Sybbie Branson, guardianAfterMothersDeath, Tom Branson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianAfterMothersDeath Context triple: [Sybbie Branson, guardianAfterMothersDeath, Tom Branson]
-
A.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
guardianInPlot
chosen
Indicates that one entity serves as a guardian or protector of another entity within the context of a specific plot or storyline.
-
C.
guardedByAfterDeath
Indicates that an entity continues to be guarded or protected by another entity after the former’s death.
-
D.
motherDeath
Indicates that the mother of the referenced individual has died.
-
E.
godmother
Indicates that one entity serves as a godmother to another, typically holding a special, often ceremonial or mentoring, parental-like role in their life.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.