Triple
T4403642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Theta platform |
E93673
|
entity |
| Predicate | fuelTypeSupport |
P11927
|
FINISHED |
| Object | gasoline |
—
|
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: gasoline | Statement: [GM Theta platform, fuelTypeSupport, gasoline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTypeSupport Context triple: [GM Theta platform, fuelTypeSupport, gasoline]
-
A.
fuelTypeSupported
chosen
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
B.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
C.
fuelSupplier
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
-
D.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
E.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
- 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_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. |
Created at: March 12, 2026, 11:28 p.m.