Triple
T29447676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6 Hours of Monza |
E746893
|
entity |
| Predicate | hostCircuitLengthApproxKm |
P69216
|
FINISHED |
| Object | 5.79 |
—
|
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: 5.79 | Statement: [6 Hours of Monza, hostCircuitLengthApproxKm, 5.79]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCircuitLengthApproxKm Context triple: [6 Hours of Monza, hostCircuitLengthApproxKm, 5.79]
-
A.
approximateCircuitLengthMi
Indicates the approximate total length of a circuit, measured in miles.
-
B.
circuitLength
Indicates the total measured length or distance of a circuit or closed path.
-
C.
approximateCircuitLength
Indicates that one entity specifies or estimates the circuit length associated with another entity.
-
D.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
E.
trackLengthApproxKm
chosen
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 3:29 p.m.