Triple
T35113836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorman, California |
E1013376
|
entity |
| Predicate | hasRoadService |
P17455
|
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: [Gorman, California, hasRoadService, gas stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadService Context triple: [Gorman, California, hasRoadService, gas stations]
-
A.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
B.
roadServed
chosen
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
C.
hasRoadCode
Indicates that an entity is associated with a specific road identification code used for classification or reference.
-
D.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:01 p.m.