Triple
T1255548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival of Festivals |
E26980
|
entity |
| Predicate | industryRole |
P8439
|
FINISHED |
| Object | platform for North American premieres |
—
|
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: platform for North American premieres | Statement: [Festival of Festivals, industryRole, platform for North American premieres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryRole Context triple: [Festival of Festivals, industryRole, platform for North American premieres]
-
A.
roleInIndustry
chosen
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
B.
careerField
Indicates the professional domain or occupational area in which an entity works or specializes.
-
C.
positionInIndustry
Indicates the role, rank, or standing that an entity holds within a particular industry or sector.
-
D.
developerOfWork
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
E.
businessCareer
Indicates a relationship where an entity’s professional life, roles, or progression is specifically within the field of business or commerce.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa726548190911b4022dc1be3c3 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.