Triple
T3761663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival de la Vézère (nearby venues) |
E82174
|
entity |
| Predicate | hasTypeOfEvents |
P14526
|
FINISHED |
| Object | classical music concerts |
—
|
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: classical music concerts | Statement: [Festival de la Vézère (nearby venues), hasTypeOfEvents, classical music concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfEvents Context triple: [Festival de la Vézère (nearby venues), hasTypeOfEvents, classical music concerts]
-
A.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
hasEventSeries
Indicates that an entity is associated with, or participates in, a sequence of related events forming a series.
-
C.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
D.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
-
E.
hasTriggerType
Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbc553a08190ba361675901496ed |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.