Triple
T30283734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giostra della Quintana |
E770173
|
entity |
| Predicate | dateRevival |
P106349
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Giostra della Quintana, dateRevival, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRevival Context triple: [Giostra della Quintana, dateRevival, 20th century]
-
A.
ideaDateBackTo
Indicates that the origin or earliest known occurrence of an idea can be traced back to a specified time or period.
-
B.
reerectionDate
Indicates the date on which something that was previously removed, dismantled, or taken down is erected or put back up again.
-
C.
recoveryDate
chosen
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
-
D.
reenvisionedDate
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
-
E.
dateReRaised
Indicates that a previously raised issue, request, or event has been brought up again on a later 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6810772408190b1d8db5d0b9bfbaa |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:45 p.m.