Triple
T13486085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreux Jazz Festival |
E318506
|
entity |
| Predicate | hasPaidEvents |
P39724
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Montreux Jazz Festival, hasPaidEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaidEvents Context triple: [Montreux Jazz Festival, hasPaidEvents, yes]
-
A.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
-
B.
hasCoSanctionedEventsWith
Indicates that two entities have jointly sanctioned or approved the same events.
-
C.
hasPayStatus
chosen
Indicates the current payment state or condition associated with an entity, such as whether an amount is paid, unpaid, pending, or otherwise resolved.
-
D.
hasCoSanctionedEventWith
Indicates that two or more entities have jointly imposed or participated in the same sanction-related event or action.
-
E.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3a15b48190b63fb59e926a97ae |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.