Triple
T28640580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaver, Utah |
E724909
|
entity |
| Predicate | hasNearbyInterstateCity |
P104638
|
FINISHED |
| Object | Cedar City, Utah |
—
|
NE NERFINISHED |
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: Cedar City, Utah | Statement: [Beaver, Utah, hasNearbyInterstateCity, Cedar City, Utah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyInterstateCity Context triple: [Beaver, Utah, hasNearbyInterstateCity, Cedar City, Utah]
-
A.
nearInterstate
Indicates that one entity is located close to or in the immediate vicinity of an interstate highway.
-
B.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
C.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
D.
hasNearbyCityFunction
chosen
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
-
E.
nearByCityState
Indicates that a city is geographically close to or within the same general area as a specified state.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 28, 2026, 4:44 a.m.