Triple
T15264841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super GT |
E364871
|
entity |
| Predicate | engineRegulationGT500 |
P84513
|
FINISHED |
| Object | 2.0-litre turbocharged inline-4 |
—
|
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: 2.0-litre turbocharged inline-4 | Statement: [Super GT, engineRegulationGT500, 2.0-litre turbocharged inline-4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineRegulationGT500 Context triple: [Super GT, engineRegulationGT500, 2.0-litre turbocharged inline-4]
-
A.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
B.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
C.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
D.
motorsportHomologationRole
Indicates the specific role or function an entity has within the homologation (official approval and certification) process in motorsport.
-
E.
engineAspiration
chosen
Indicates whether and how an engine’s intake air is boosted or modified (e.g., naturally aspirated, turbocharged, supercharged).
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.