Triple
T35023608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Beaver Creek |
E1010262
|
entity |
| Predicate | usedAsAccessRouteTo |
P41137
|
FINISHED |
| Object | Picket Range |
—
|
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: Picket Range | Statement: [Big Beaver Creek, usedAsAccessRouteTo, Picket Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsAccessRouteTo Context triple: [Big Beaver Creek, usedAsAccessRouteTo, Picket Range]
-
A.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
B.
accessedThrough
chosen
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
C.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
D.
usedAsTransitRouteFor
Indicates that something serves as a pathway or channel through which another entity is transported or moved.
-
E.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.