Triple
T10982643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autoroute A13 |
E259545
|
entity |
| Predicate | regulatesTrafficBy |
P17040
|
FINISHED |
| Object | variable message signs |
—
|
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: variable message signs | Statement: [Autoroute A13, regulatesTrafficBy, variable message signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesTrafficBy Context triple: [Autoroute A13, regulatesTrafficBy, variable message signs]
-
A.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
B.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
-
C.
hasTrafficRegime
Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
-
D.
relievesTrafficFrom
Indicates that one entity reduces or alleviates traffic congestion that would otherwise occur on another entity.
-
E.
hasTrafficControl
chosen
Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772eb518c8190a885a417815f2ff6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.