Triple
T29447672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6 Hours of Monza |
E746893
|
entity |
| Predicate | multiClass |
P55157
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [6 Hours of Monza, multiClass, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiClass Context triple: [6 Hours of Monza, multiClass, true]
-
A.
defaultMultiClass
chosen
Indicates that an entity is configured to support or operate in multiple classes or categories by default.
-
B.
classificationConsensus
Indicates that multiple agents or sources agree on the same classification or category assignment for a given entity or item.
-
C.
usedToClassify
Indicates that one entity serves as a criterion or basis for categorizing or grouping another entity.
-
D.
aimOfClassification
Indicates that one entity represents the purpose, goal, or intended outcome of a particular act or system of classification applied to another entity.
-
E.
classificationTest
Indicates that an entity is involved in or associated with a test or evaluation process used for classification purposes.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 3:29 p.m.