Triple
T22287272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercontinental Le Mans Cup |
E550895
|
entity |
| Predicate | classIncluded |
P131580
|
FINISHED |
| Object | LMP1 |
—
|
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: LMP1 | Statement: [Intercontinental Le Mans Cup, classIncluded, LMP1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classIncluded Context triple: [Intercontinental Le Mans Cup, classIncluded, LMP1]
-
A.
includesClasses
chosen
Indicates that one entity contains or encompasses one or more class-type entities as part of its definition or structure.
-
B.
hasIncluded
Indicates that one entity has incorporated or contained another entity as part of itself or within its scope.
-
C.
programIncluded
Indicates that a particular program is contained within, or forms part of, another specified collection, package, or set of programs.
-
D.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
E.
initiallyIncluded
Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560896348190985725ac8ad406b3 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.