Triple
T29541324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Gas |
E749506
|
entity |
| Predicate | fuelTypeSupplied |
P11818
|
FINISHED |
| Object | natural gas |
—
|
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: natural gas | Statement: [Osaka Gas, fuelTypeSupplied, natural gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTypeSupplied Context triple: [Osaka Gas, fuelTypeSupplied, natural gas]
-
A.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
-
B.
fleetFuelType
Indicates the type of fuel used by a fleet as a whole or by vehicles within that fleet.
-
C.
fuelForm
chosen
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
D.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
E.
fuelCharacteristic
Indicates a relationship where a fuel is associated with one of its defining properties or qualities, such as composition, performance, or behavior.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ccb2f0c8190afec245ff546681c |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:02 p.m.