Triple
T9742161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Documentary Competition |
E236210
|
entity |
| Predicate | festivalScope |
P44899
|
FINISHED |
| Object | independent film |
—
|
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: independent film | Statement: [U.S. Documentary Competition, festivalScope, independent film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalScope Context triple: [U.S. Documentary Competition, festivalScope, independent film]
-
A.
festivalFocus
chosen
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
B.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
C.
festivalSeason
Indicates that a time period is designated or recognized as the season during which a particular festival or set of festivals takes place.
-
D.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
E.
exampleFestival
Indicates that an entity is an instance or example of a particular festival event or type of festival.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2cb7008190a829a03114d6c704 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.