Triple
T17640779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix for best performer |
E429216
|
entity |
| Predicate | relatedFestivalType |
P128363
|
FINISHED |
| Object | international arts 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 arts festival | Statement: [Grand Prix for best performer, relatedFestivalType, international arts festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedFestivalType Context triple: [Grand Prix for best performer, relatedFestivalType, international arts festival]
-
A.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
-
B.
linksFestivalTo
Indicates that one entity is associated with, connected to, or participates in a particular festival.
-
C.
relationToMainFestival
Indicates how a given event, activity, or element is connected or related to the main festival.
-
D.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
E.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de50bf481909e938613b38f0202 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 6:02 a.m.