Triple
T29447683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6 Hours of Monza |
E746893
|
entity |
| Predicate | allowsDriverChanges |
P180438
|
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, allowsDriverChanges, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsDriverChanges Context triple: [6 Hours of Monza, allowsDriverChanges, true]
-
A.
hasDriverChangeRequirement
Indicates that a situation or configuration requires a change of driver to proceed or remain valid.
-
B.
canChangeIn
Indicates that one entity is capable of undergoing alteration, transformation, or variation within the context or influence of another entity or condition.
-
C.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
D.
allowsCupDrivers
Indicates that one entity grants permission or authorization for Cup drivers to participate in or make use of another entity.
-
E.
canBeReconfigured
Indicates that one entity has the capability to be altered, adjusted, or rearranged into a different configuration, typically under certain conditions or using specific methods.
- F. None of above. chosen
Provenance (4 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 28, 2026, 3:29 p.m.