Triple
T18140067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte for Ever |
E434236
|
entity |
| Predicate | directorFatherOfLeadActress |
P130601
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Charlotte for Ever, directorFatherOfLeadActress, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorFatherOfLeadActress Context triple: [Charlotte for Ever, directorFatherOfLeadActress, true]
-
A.
directorOfWorkFeaturingSubject
Indicates that the subject is the director of a creative work in which another specified entity appears or is featured.
-
B.
directorSince
Indicates that one entity has held the role of director for another entity starting from a specified point in time.
-
C.
directorSpouseInCast
Indicates that a film’s director is married to someone who appears as a cast member in that same film.
-
D.
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).
-
E.
creatorFather
Indicates that one entity is the male parent (father) who created, generated, or brought into existence the other entity.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0a59d08190be74c1ecc00a8f3a |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.