Triple
T33703012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel (Love Actually) |
E863508
|
entity |
| Predicate | hasChildInCare |
P196960
|
FINISHED |
| Object | Sam (Love Actually) |
—
|
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: Sam (Love Actually) | Statement: [Daniel (Love Actually), hasChildInCare, Sam (Love Actually)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildInCare Context triple: [Daniel (Love Actually), hasChildInCare, Sam (Love Actually)]
-
A.
hasChildCare
Indicates that an entity provides, offers, or is associated with child care services or facilities for children.
-
B.
legalStatusAsChildOf
Indicates that one entity holds a specific legal status or recognition in relation to being the child of another entity.
-
C.
hasParentalUnit
Indicates that an entity has a parent or guardian that serves as its primary caregiving or parental figure.
-
D.
hasFosterFamily
Indicates that an entity is placed with and cared for by a foster family, rather than its original or biological family.
-
E.
hasChildWhoBecame
Indicates that an entity has a child who later attained or transitioned into a specified role, status, or condition.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 1, 2026, 1:43 a.m.