Triple
T34249430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocco and His Brothers (film score) |
E878697
|
entity |
| Predicate | hasOriginalFilmTitle |
P108532
|
FINISHED |
| Object | Rocco e i suoi fratelli |
—
|
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: Rocco e i suoi fratelli | Statement: [Rocco and His Brothers (film score), hasOriginalFilmTitle, Rocco e i suoi fratelli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalFilmTitle Context triple: [Rocco and His Brothers (film score), hasOriginalFilmTitle, Rocco e i suoi fratelli]
-
A.
hasOriginalTitleScript
Indicates that an entity’s original title is written or represented in a specific writing system or script.
-
B.
originallyTitleOf
Indicates that one title is the original title from which another work, edition, or localized title is derived.
-
C.
originalTitleName
chosen
Indicates that one entity is the original or primary title name associated with another entity.
-
D.
hasOriginalWorkEnglishTitle
Indicates that an entity has an associated original work whose title is given in English.
-
E.
hasOriginalTitleMeaning
Indicates that an entity’s original title conveys or is associated with a particular meaning or interpretation.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 1, 2026, 1:56 a.m.