Triple
T23187169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beale Street Music Festival |
E579621
|
entity |
| Predicate | approximateTimeOfYear |
P99273
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Beale Street Music Festival, approximateTimeOfYear, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateTimeOfYear Context triple: [Beale Street Music Festival, approximateTimeOfYear, spring]
-
A.
approximateTimeInYear
chosen
Indicates that one time-related entity represents an estimated or non-exact point or interval within a given year for another entity.
-
B.
timeOfYearPresented
Indicates the specific time or season of the year during which something is presented or takes place.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
approximateTimeOfDayOfEventCommemorated
Indicates the general time of day during which the commemorated event is understood to have occurred.
-
E.
approximateDateChange
Indicates that the date associated with an entity has changed in an inexact or estimated manner rather than to a precisely known new date.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd4c6f481908b6138a44b98c8a7 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.