Triple
T29957927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Youphoria Stage |
E760958
|
entity |
| Predicate | languageOfFestivalEnvironment |
P115943
|
FINISHED |
| Object | multilingual |
—
|
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: multilingual | Statement: [The Youphoria Stage, languageOfFestivalEnvironment, multilingual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfFestivalEnvironment Context triple: [The Youphoria Stage, languageOfFestivalEnvironment, multilingual]
-
A.
languageOfEnvironment
Indicates the language predominantly used or present in a given environment or context.
-
B.
primaryFestivalLanguage
chosen
Indicates that a particular language is the main or officially designated language used for communication and activities at a festival.
-
C.
languageOfVenue
Indicates the language primarily used or officially designated for communication at a given venue.
-
D.
languageOfEvent
Indicates the language in which an event is conducted, presented, or communicated.
-
E.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 29, 2026, 6:27 p.m.