Triple
T16067908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Motor Manufacturing Texas |
E389778
|
entity |
| Predicate | hasPrimaryFuelType |
P11927
|
FINISHED |
| Object | electricity |
—
|
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: electricity | Statement: [Toyota Motor Manufacturing Texas, hasPrimaryFuelType, electricity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFuelType Context triple: [Toyota Motor Manufacturing Texas, hasPrimaryFuelType, electricity]
-
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.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in time.
-
C.
fuelTypeProduced
Indicates the type of fuel that is generated or produced by a given source, process, or facility.
-
D.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
E.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.