Triple
T34249479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nights of Cabiria (film score) |
E878699
|
entity |
| Predicate | forWorkDirector |
P32895
|
FINISHED |
| Object | Federico Fellini |
E239363
|
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: Federico Fellini | Statement: [Nights of Cabiria (film score), forWorkDirector, Federico Fellini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forWorkDirector Context triple: [Nights of Cabiria (film score), forWorkDirector, Federico Fellini]
-
A.
workDirector
chosen
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
B.
basedOnWorkDirector
Indicates that one entity serves as the director of a work on which another entity is based.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
E.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
- F. None of above.
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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36d5f166248190a4b8c199f268a6f5 |
completed | June 20, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.