Triple
T34541993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POSTROUTING |
E886827
|
entity |
| Predicate | effectOnRouting |
P193080
|
FINISHED |
| Object | does not change routing decision |
—
|
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: does not change routing decision | Statement: [POSTROUTING, effectOnRouting, does not change routing decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnRouting Context triple: [POSTROUTING, effectOnRouting, does not change routing decision]
-
A.
effectOnPath
Indicates the influence or change that one entity or action has on the course, route, or trajectory of another.
-
B.
routeAffected
Indicates that a transportation route is impacted or disrupted in some way, such as by delays, closures, or changes in service.
-
C.
effectOnRecipient
Indicates the impact, change, or consequence that an action or event has on the recipient entity.
-
D.
effectOnOutput
Indicates how one factor, action, or condition influences or changes the resulting output of a process or system.
-
E.
effectOnUsage
Indicates how one factor or condition changes the way something is used, including the extent, manner, or frequency of its usage.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 1, 2026, 2:02 a.m.