Triple
T25771645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palio di Siena |
E649035
|
entity |
| Predicate | CorteoStoricoFeatures |
P18777
|
FINISHED |
| Object | flags and drummers |
—
|
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: flags and drummers | Statement: [Palio di Siena, CorteoStoricoFeatures, flags and drummers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CorteoStoricoFeatures Context triple: [Palio di Siena, CorteoStoricoFeatures, flags and drummers]
-
A.
isHeritageRoute
Indicates that a route is officially recognized or designated as a heritage route, typically due to its historical, cultural, or natural significance.
-
B.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
-
C.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
D.
historicalCharacteristic
chosen
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
E.
featuresHistorian
Indicates that something includes or presents a historian as a notable participant, subject, or element.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf84fb88190b40280340332743e |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 5:30 a.m.