Triple
T34249421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocco and His Brothers (film score) |
E878697
|
entity |
| Predicate | associatedPlaceOfFilm |
P4373
|
FINISHED |
| Object | Milan |
E11464
|
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: Milan | Statement: [Rocco and His Brothers (film score), associatedPlaceOfFilm, Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPlaceOfFilm Context triple: [Rocco and His Brothers (film score), associatedPlaceOfFilm, Milan]
-
A.
formerFilmingLocation
Indicates that a place was once used as a filming location for a work but is no longer used for that purpose.
-
B.
filmLocationFor
chosen
Indicates a relationship where a specific place serves as the filming location for a particular film or production.
-
C.
filmingLocationContext
Indicates the contextual relationship specifying where the filming of an event, scene, or production took place.
-
D.
notableFilmingLocation
Indicates that a place served as a significant or well-known location where a film or television production was shot.
-
E.
filmingLocationForAdaptation
Indicates the place where an adaptation (such as a film or TV version of a work) was shot or recorded.
- 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e61e6a488190963d23a8a2882782 |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.