Triple
T1108849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tin Lizzie |
E25545
|
entity |
| Predicate | associatedWithFuelEconomy |
P23422
|
FINISHED |
| Object | roughly 13–21 miles per gallon |
—
|
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: roughly 13–21 miles per gallon | Statement: [Tin Lizzie, associatedWithFuelEconomy, roughly 13–21 miles per gallon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFuelEconomy Context triple: [Tin Lizzie, associatedWithFuelEconomy, roughly 13–21 miles per gallon]
-
A.
typicalFuel
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
-
B.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
C.
relatedVehicle
Indicates that there exists an associated or connected vehicle that has a relevant relationship to the primary entity.
-
D.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
E.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
- F. None of above. chosen
Provenance (4 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e6134481909f348986a25f65c6 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b749e2a881909ef28745a7d2d917 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:43 p.m.