Triple
T33930212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack (2014 film) |
E869868
|
entity |
| Predicate | festivalSelectionType |
P177920
|
FINISHED |
| Object | competition |
—
|
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: competition | Statement: [Jack (2014 film), festivalSelectionType, competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalSelectionType Context triple: [Jack (2014 film), festivalSelectionType, competition]
-
A.
festivalTypeHosted
Indicates that a particular location or organizer hosts festivals of a specified type.
-
B.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
C.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
-
D.
categoryWithinFestival
Indicates that one category or sub-event is part of, or occurs within the scope of, a particular festival.
-
E.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
- F. None of above. chosen
Provenance (4 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.