Triple
T29447703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMP1 (historic) |
E746894
|
entity |
| Predicate | topLevelClassInEvent |
P10192
|
FINISHED |
| Object | 24 Hours of Le Mans |
—
|
NE NERFINISHED |
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: 24 Hours of Le Mans | Statement: [LMP1 (historic), topLevelClassInEvent, 24 Hours of Le Mans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelClassInEvent Context triple: [LMP1 (historic), topLevelClassInEvent, 24 Hours of Le Mans]
-
A.
topClassOf
Indicates that one class is the most general or highest-level superclass from which another class (or set of classes) ultimately derives.
-
B.
topLevelOf
chosen
Indicates that one entity is the highest or most overarching level within the structure or hierarchy of another entity.
-
C.
mainEventClass
Indicates that an event is classified as the primary or most central event within a given context or dataset.
-
D.
topLevelHierarchy
Indicates that an entity occupies the highest position or root level within a hierarchical structure, with no parent above it.
-
E.
topLevel
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above 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_69f66b21ea908190ae69b3f802fadab1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:29 p.m.