Triple
T32620818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love You More |
E833916
|
entity |
| Predicate | directorBirthName |
P193847
|
FINISHED |
| Object | Sam Taylor-Wood |
—
|
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 Taylor-Wood | Statement: [Love You More, directorBirthName, Sam Taylor-Wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorBirthName Context triple: [Love You More, directorBirthName, Sam Taylor-Wood]
-
A.
creatorBirthName
Indicates the full birth name originally given to the creator of a work or entity.
-
B.
directorFullName
Indicates that the predicate specifies the complete name of the person who serves as the director in the described relationship or context.
-
C.
authorBirthName
Indicates the full personal name an author was given at birth, before any later name changes or pseudonyms.
-
D.
directorSince
Indicates that one entity has held the role of director for another entity starting from a specified point in time.
-
E.
directorAssociatedWith
Indicates a relationship where a director is professionally connected to, responsible for, or involved with a particular entity (such as a work, organization, or project).
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 1, 2026, 1:06 a.m.