Triple
T23906377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London After Midnight |
E601207
|
entity |
| Predicate | remakeDirectedBy |
P25829
|
FINISHED |
| Object | Tod Browning |
—
|
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: Tod Browning | Statement: [London After Midnight, remakeDirectedBy, Tod Browning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remakeDirectedBy Context triple: [London After Midnight, remakeDirectedBy, Tod Browning]
-
A.
remakeDirector
chosen
Indicates that the subject is the director of a remake of the object work (e.g., film, show, or other media).
-
B.
remakeOfFilmStarring
Indicates that one film is a remake of another film in which a specified actor or set of actors starred.
-
C.
laterDirectedBy
Indicates that one entity was directed by another entity at a later time than some referenced or implied directing event.
-
D.
isDirectedBy
Indicates that one entity serves as the director or guiding authority responsible for the creation, management, or execution of another entity (such as a film, project, or organization).
-
E.
remakeFeature
Indicates that one work is a new version or adaptation created by redoing or updating the features of an earlier work.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce91144c8190b894e25a45dfd7c9 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:35 p.m.