Triple
T3853755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival Radio France Occitanie Montpellier |
E85360
|
entity |
| Predicate | typicalEventPeriod |
P35710
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [Festival Radio France Occitanie Montpellier, typicalEventPeriod, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEventPeriod Context triple: [Festival Radio France Occitanie Montpellier, typicalEventPeriod, summer]
-
A.
typicalEventDay
Indicates the day on which an event is normally or most commonly held or occurs.
-
B.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
timePeriodEvent
chosen
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
D.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
E.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec0438308190865ff74bee5a1cf2 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.