Triple
T4313470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Choice Award |
E94130
|
entity |
| Predicate | associatedWithFestivalType |
P22569
|
FINISHED |
| Object | international film festival |
—
|
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: international film festival | Statement: [People’s Choice Award, associatedWithFestivalType, international film festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFestivalType Context triple: [People’s Choice Award, associatedWithFestivalType, international film festival]
-
A.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
-
B.
hasFestivityType
chosen
Indicates that an event or celebration is classified as belonging to a particular type of festivity.
-
C.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
D.
relationToMainFestival
Indicates how a given event, activity, or element is connected or related to the main festival.
-
E.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f319c08190bb40a9fc5933728d |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.