Triple
T31343230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-340 road |
E799365
|
entity |
| Predicate | hasBypassedSections |
P171258
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [N-340 road, hasBypassedSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBypassedSections Context triple: [N-340 road, hasBypassedSections, yes]
-
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.
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).
-
C.
bypassedSince
Indicates that one entity has been avoided, skipped, or circumvented by another entity starting from a specific point in time and continuing thereafter.
-
D.
bypassedVia
Indicates that one entity is avoided, skipped, or circumvented by using another specified means, route, or method.
-
E.
bypassedLocation
Indicates that an entity intentionally passed by or went around a specific location without stopping or entering it.
- F. None of above. chosen
Provenance (4 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f15d4f8819098892ed7905af38c |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:17 p.m.