Triple
T31061302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q44 Select Bus Service |
E791546
|
entity |
| Predicate | usesBusFuelType |
P159873
|
FINISHED |
| Object | diesel-electric hybrid |
—
|
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: diesel-electric hybrid | Statement: [Q44 Select Bus Service, usesBusFuelType, diesel-electric hybrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBusFuelType Context triple: [Q44 Select Bus Service, usesBusFuelType, diesel-electric hybrid]
-
A.
fleetFuelType
chosen
Indicates the type of fuel used by a fleet as a whole or by vehicles within that fleet.
-
B.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in time.
-
C.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
D.
fuelRole
Indicates that one entity serves as the fuel or energy source used or consumed by another entity in a process or operation.
-
E.
fuelTransport
Indicates the transfer or conveyance of fuel from one location or entity to another.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 9:01 p.m.