Triple
T21685984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palio di Asti |
E535228
|
entity |
| Predicate | hasPreliminaryEvents |
P12109
|
FINISHED |
| Object | qualifying heats |
—
|
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: qualifying heats | Statement: [Palio di Asti, hasPreliminaryEvents, qualifying heats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreliminaryEvents Context triple: [Palio di Asti, hasPreliminaryEvents, qualifying heats]
-
A.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
B.
hasPreliminaryRounds
chosen
Indicates that an event, competition, or process includes one or more initial qualifying rounds before the main or final stage.
-
C.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
-
D.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
E.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cb69f081908ed0c7ebea429898 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.