Triple
T30538095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calso |
E777202
|
entity |
| Predicate | fuelStationType |
P27765
|
FINISHED |
| Object | full-service gasoline stations |
—
|
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: full-service gasoline stations | Statement: [Calso, fuelStationType, full-service gasoline stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelStationType Context triple: [Calso, fuelStationType, full-service gasoline stations]
-
A.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
B.
fleetFuelType
Indicates the type of fuel used by a fleet as a whole or by vehicles within that fleet.
-
C.
fuelSupplier
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
-
D.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in time.
-
E.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f688520c60819081c3365a0f944326 |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:19 p.m.