Triple
T16596990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giro di Sicilia |
E403232
|
entity |
| Predicate | revivalEdition |
P66426
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Giro di Sicilia, revivalEdition, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalEdition Context triple: [Giro di Sicilia, revivalEdition, 2019]
-
A.
revivalVersionProducedFor
Indicates that a specific version of a revived work (such as a reboot, remake, or updated edition) was produced for a particular entity, context, or release.
-
B.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
C.
revivalVersionAssociatedWith
Indicates that one version or edition is linked to its corresponding revival or reissued version.
-
D.
revivalVersionChartedOn
Indicates that a particular revival version of a work is recorded as having appeared on a specific chart.
-
E.
revivalVersionLabel
chosen
Indicates the specific version identifier or label associated with a revival or restored instance of something (e.g., a document, work, or system).
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d723c508190b5afbda5eec5abea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.