Triple
T21654834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 288 |
E534431
|
entity |
| Predicate | bypassFor |
P124712
|
FINISHED |
| Object | through traffic around Richmond |
—
|
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: through traffic around Richmond | Statement: [State Route 288, bypassFor, through traffic around Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bypassFor Context triple: [State Route 288, bypassFor, through traffic around Richmond]
-
A.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
B.
bypassedVia
chosen
Indicates that one entity is avoided, skipped, or circumvented by using another specified means, route, or method.
-
C.
bypassFunction
Indicates that one function or process is used to circumvent, skip, or avoid the normal behavior or execution path of another function or mechanism.
-
D.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
E.
bypassName
Indicates that an entity is known or referred to by an alternative name used specifically for bypassing or circumventing a standard process, route, or restriction.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59176b28819092384fc5f8968022 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.