Triple
T14582560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 169 |
E342227
|
entity |
| Predicate | hasBypassSections |
P113407
|
FINISHED |
| Object | around some cities |
—
|
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: around some cities | Statement: [U.S. Route 169, hasBypassSections, around some cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBypassSections Context triple: [U.S. Route 169, hasBypassSections, around some cities]
-
A.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
B.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
C.
bypassedLocation
Indicates that an entity intentionally passed by or went around a specific location without stopping or entering it.
-
D.
hasElevatedSections
Indicates that one entity contains or features parts that are raised or elevated relative to its other sections.
-
E.
bypassesCity
chosen
Indicates that a route, road, or path goes around a city rather than passing directly through it.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb41e71748190a1deacc819dd26d3 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.