Triple
T18806199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Per Saari |
E459879
|
entity |
| Predicate | roleAtBlossomFilms |
P55759
|
FINISHED |
| Object | producer |
—
|
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: producer | Statement: [Per Saari, roleAtBlossomFilms, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBlossomFilms Context triple: [Per Saari, roleAtBlossomFilms, producer]
-
A.
roleInFilmEcosystem
chosen
Indicates the specific function or position an entity holds within the broader network of activities, stakeholders, and processes that make up the film ecosystem.
-
B.
roleInCinerama
Indicates that an entity has a role or participation in a Cinerama film or production.
-
C.
ownedByInFilm
Indicates that one entity is portrayed as being owned or possessed by another entity within the context of a specific film.
-
D.
subsidiaryRoleOfGeneralFilmCompany
Indicates that an entity serves as a subsidiary or subordinate unit within the General Film Company.
-
E.
developerOfWorkAppearingIn
Indicates that one entity is the creator or developer of a work in which another entity appears or is featured.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d7f8d08190a3e02fab6dc40bb5 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.