Triple
T367761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle International Film Festival |
E7999
|
entity |
| Predicate | programsInclude |
P10191
|
FINISHED |
| Object | gala screenings |
—
|
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: gala screenings | Statement: [Seattle International Film Festival, programsInclude, gala screenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programsInclude Context triple: [Seattle International Film Festival, programsInclude, gala screenings]
-
A.
programmingIncludes
chosen
Indicates that one programming-related entity contains, incorporates, or makes use of another as a part, feature, or component.
-
B.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
C.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
D.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebeab13c8190b15c2f10310ec6a8 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.