Triple
T18806211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Per Saari |
E459879
|
entity |
| Predicate | companyFoundedYear |
P4025
|
FINISHED |
| Object | Blossom Films – late 2000s |
—
|
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: Blossom Films – late 2000s | Statement: [Per Saari, companyFoundedYear, Blossom Films – late 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyFoundedYear Context triple: [Per Saari, companyFoundedYear, Blossom Films – late 2000s]
-
A.
coFoundedInYear
Indicates that two or more entities jointly founded something (such as an organization or company) in a specified year.
-
B.
foundedAt
chosen
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
C.
companyFoundedFocus
Indicates that a company was founded with a particular primary focus, such as a specific industry, mission, or area of activity.
-
D.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
E.
companyFoundedWith
Indicates that a company was established using or in association with a particular resource, organization, or founding context.
- 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.