Triple
T1915160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muni bus network |
E39999
|
entity |
| Predicate | usesVehicleFuel |
P22119
|
FINISHED |
| Object | diesel |
—
|
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 | Statement: [Muni bus network, usesVehicleFuel, diesel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVehicleFuel Context triple: [Muni bus network, usesVehicleFuel, diesel]
-
A.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
B.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
C.
typicalFuel
chosen
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
-
D.
associatedWithFuelEconomy
Indicates a relationship where something is connected or relevant to fuel economy, such as influencing, measuring, or describing fuel efficiency.
-
E.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.