Triple
T6535727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan International Film Festival Organizing Committee |
E152356
|
entity |
| Predicate | typeOfEventOrganized |
P34559
|
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: [Busan International Film Festival Organizing Committee, typeOfEventOrganized, international film festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEventOrganized Context triple: [Busan International Film Festival Organizing Committee, typeOfEventOrganized, international film festival]
-
A.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
B.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
C.
eventTypeOrganized
chosen
Indicates that an entity organized or arranged a specific type or category of event.
-
D.
typeOfEventForStart
Indicates the specific kind or category of event that marks the beginning of something.
-
E.
hostsTypeOfEvent
Indicates that an entity organizes or provides the venue for a particular type or category of 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adc238688190aca143b22b8a399c |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.