Triple
T33127756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autoroutes Paris-Rhin-Rhône |
E847764
|
entity |
| Predicate | monitorsTraffic |
P77923
|
FINISHED |
| Object | on its motorway network |
—
|
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: on its motorway network | Statement: [Autoroutes Paris-Rhin-Rhône, monitorsTraffic, on its motorway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsTraffic Context triple: [Autoroutes Paris-Rhin-Rhône, monitorsTraffic, on its motorway network]
-
A.
hasTrafficMonitoring
chosen
Indicates that an entity is equipped with or associated with a system or capability for observing, measuring, or analyzing traffic conditions or flows.
-
B.
trafficServed
Indicates that a system, component, or entity handles, processes, or carries a specified amount or type of traffic (e.g., network, data, or user requests).
-
C.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
D.
hasTrafficPattern
Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
-
E.
carriedTraffic
Indicates that one entity transported, transmitted, or bore the flow of traffic (such as data, vehicles, or signals) for another entity or along a route.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d7216ab08190889db6236a2cacf5 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.