Triple
T26037094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaton Sound festival site |
E647581
|
entity |
| Predicate | approximateUseFrequency |
P65602
|
FINISHED |
| Object | annual 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: annual festival | Statement: [Balaton Sound festival site, approximateUseFrequency, annual festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateUseFrequency Context triple: [Balaton Sound festival site, approximateUseFrequency, annual festival]
-
A.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
B.
hasApproximateUse
Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
-
C.
suggestsFrequencyNear
chosen
Indicates that one entity proposes or implies an approximate or nearby frequency value relative to another entity.
-
D.
isMoreFrequentlyUsedThan
Indicates that one entity is used or occurs with greater frequency than another entity.
-
E.
recommendedUsageFrequency
Indicates how often something is advised or prescribed to be used within a given time period.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 22, 2026, 9:08 a.m.