Triple
T22549120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral Valley |
E557508
|
entity |
| Predicate | roadHazard |
P78490
|
FINISHED |
| Object | deep sand |
—
|
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: deep sand | Statement: [Cathedral Valley, roadHazard, deep sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadHazard Context triple: [Cathedral Valley, roadHazard, deep sand]
-
A.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
-
B.
roadAffected
Indicates that a road is impacted or disrupted by a condition, event, or action, such as construction, accidents, or adverse weather.
-
C.
hasRoadCondition
chosen
Indicates that a specified road segment possesses or is characterized by a particular condition or state (e.g., quality, surface, or status).
-
D.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
E.
roadOften
Indicates that the road is frequently used, traveled, or encountered in the relevant context.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f74512c8190b5369e19a4bc6325 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.