Triple
T31121420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nero-Film |
E793232
|
entity |
| Predicate | notableDirectorWorkedWith |
P207362
|
FINISHED |
| Object | Fritz Lang |
E43220
|
NE 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: Fritz Lang | Statement: [Nero-Film, notableDirectorWorkedWith, Fritz Lang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDirectorWorkedWith Context triple: [Nero-Film, notableDirectorWorkedWith, Fritz Lang]
-
A.
notableCastWorkedWith
Indicates that there is a notable professional collaboration or working relationship between members of a cast.
-
B.
workOfDirectorKnownFor
Indicates that a work (such as a film or show) is directed by a person for whom this work is one of their notable or best-known creations.
-
C.
filmDirectorWorkedWith
Indicates that a film director has collaborated professionally with another person on one or more film projects.
-
D.
notableDirector
Indicates that a person has directed a work (such as a film or show) in a way that is recognized as significant or distinguished.
-
E.
coDirectedWith
Indicates that two or more entities jointly directed the same work or project.
- F. None of above. chosen
Provenance (5 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2938bf1b008190bc564faa0d2ffa00 |
completed | June 10, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:04 p.m.