Triple
T4403640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Theta platform |
E93673
|
entity |
| Predicate | engineConfigurationSupport |
P56053
|
FINISHED |
| Object | inline-four engines |
—
|
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: inline-four engines | Statement: [GM Theta platform, engineConfigurationSupport, inline-four engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineConfigurationSupport Context triple: [GM Theta platform, engineConfigurationSupport, inline-four engines]
-
A.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
B.
engineSupplier
Indicates a relationship where one entity supplies or provides engines to another entity.
-
C.
secondGenerationEngineOption
Indicates that an entity offers or is associated with a second-generation version of an engine as an available option.
-
D.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
E.
engineCode
Indicates a relationship where an entity is associated with a specific engine identification code or designation.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d1af608190ac06d50433cf24bb |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3509997208190933f167f7e20ccfa |
completed | March 12, 2026, 11:47 p.m. |
Created at: March 12, 2026, 11:28 p.m.