Triple
T37758429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PA 12 |
E941184
|
entity |
| Predicate | hasBypassSection |
P12840
|
FINISHED |
| Object | Warren Street Bypass |
—
|
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: Warren Street Bypass | Statement: [PA 12, hasBypassSection, Warren Street Bypass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBypassSection Context triple: [PA 12, hasBypassSection, Warren Street Bypass]
-
A.
hasBypassedSections
Indicates that certain sections within a process, route, or structure have been skipped, avoided, or not traversed as part of the overall path or execution.
-
B.
hasBypass
chosen
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
C.
hasBypassProject
Indicates that an entity is associated with a project designed to bypass, circumvent, or provide an alternative route around something (such as a system, process, or constraint).
-
D.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
E.
bypassedVia
Indicates that one entity is avoided, skipped, or circumvented by using another specified means, route, or method.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef7b6c48190b99d82da5594889c |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.