Triple
T8371713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abwehr |
E197474
|
entity |
| Predicate | directorStartTime |
P2488
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Abwehr, directorStartTime, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorStartTime Context triple: [Abwehr, directorStartTime, 1935]
-
A.
directorStartYear
chosen
Indicates the year in which an individual began serving as a director (e.g., of a film, organization, or project).
-
B.
directorSince
Indicates that one entity has held the role of director for another entity starting from a specified point in time.
-
C.
featureDirectorialDebutOf
Indicates that a work (typically a film) serves as the first directorial effort of a particular director.
-
D.
filmDebut
Indicates the first film in which an entity (typically a person) appeared or participated, marking their initial entry into film work.
-
E.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a509dc81909e0ea4c66b21d84f |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.