Triple
T23005285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom City, Missouri |
E572747
|
entity |
| Predicate | hasRoadsideServices |
P107291
|
FINISHED |
| Object | gas 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: gas stations | Statement: [Kingdom City, Missouri, hasRoadsideServices, gas stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadsideServices Context triple: [Kingdom City, Missouri, hasRoadsideServices, gas stations]
-
A.
hasRoadsideFacility
chosen
Indicates that a location or route segment is associated with a facility or service situated along its roadside.
-
B.
hasRestAreas
Indicates that a route, location, or facility includes one or more designated rest areas available for use.
-
C.
hasFuelServices
Indicates that one entity provides or is equipped with fuel-related services or facilities for another entity.
-
D.
hasServiceStationNetworkIn
Indicates that an entity operates or maintains a network of service stations within a specified geographic area or region.
-
E.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18356417881908c8d6ee56bdc85f5 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.