Triple
T24147510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 52 |
E598425
|
entity |
| Predicate | isDiagonalRoute |
P130287
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [U.S. Route 52, isDiagonalRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiagonalRoute Context triple: [U.S. Route 52, isDiagonalRoute, true]
-
A.
isRadialRouteOf
Indicates that one route functions as a radial connection extending outward from a central point, hub, or main route.
-
B.
runsDiagonally
chosen
Indicates that one entity extends or moves in a diagonal direction relative to another reference frame or axis.
-
C.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
D.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
E.
diagonalProperty
Indicates a relationship where something possesses or exhibits a diagonal characteristic, alignment, or behavior relative to a reference frame or structure.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00c42288190843962f9476a94a1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.