Triple
T21685976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palio di Asti |
E535228
|
entity |
| Predicate | hasLaps |
P42384
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Palio di Asti, hasLaps, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaps Context triple: [Palio di Asti, hasLaps, three]
-
A.
hasLapStructure
Indicates that an entity possesses a lap-like structural configuration or component as part of its overall form or design.
-
B.
typicalRaceDistanceLaps
chosen
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
-
C.
hasLapRecordCategory
Indicates that an entity holds or is associated with a specific category or type of lap record (e.g., fastest lap under certain conditions or classifications).
-
D.
numberOfLapsVariesByClass
Indicates that the number of laps completed or required differs depending on the class or category involved in the event or activity.
-
E.
hasPaceGroups
Indicates that an event or activity is organized into distinct groups based on participants’ pace or speed.
- 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.