Triple
T16303114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Hours of Le Mans |
E395838
|
entity |
| Predicate | historicStartFormat |
P122605
|
FINISHED |
| Object | Le Mans start |
—
|
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: Le Mans start | Statement: [24 Hours of Le Mans, historicStartFormat, Le Mans start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicStartFormat Context triple: [24 Hours of Le Mans, historicStartFormat, Le Mans start]
-
A.
historicalFormat
Indicates that something is presented or recorded in a format that was used in the past, reflecting its historical or legacy form.
-
B.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
C.
formatHistory
Indicates that one entity records or structures the sequence of past states, events, or changes associated with another entity into a specific format.
-
D.
dateFormat
Indicates the specific pattern or structure used to represent a date as a formatted string.
-
E.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.