Triple
T21442931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EN |
E528984
|
entity |
| Predicate | usedInTrafficReports |
P77923
|
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: [EN, usedInTrafficReports, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTrafficReports Context triple: [EN, usedInTrafficReports, yes]
-
A.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
B.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
C.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
D.
hasCommuterTraffic
Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
-
E.
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.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b7044a3881908a7fe26f26c92762 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.